if on a running workflow, dagman goes away suddenly ( lets say because of power failure ), the dagman finished event is not logged in the dagman out file. when condor comes up again a new dagman instance is started.

monitord in this case should warn about the case, and add a dagman finished event when it see's dagman starting again without it having ended earlier. this is to ensure that the workflow states are matched up in teh workflow state table