Some failed steps report bad running time

[initialcontext]

We check at the end of each step to capture the full step running times. We need to reject tasks minStartTimes that erroneously report 0 (or anything less than full workflow start time) for this to avoid ending up with a UNIX timestamp instead of a task duration in seconds.

[initialcontext]

i am pushing a fix for the case where calls to FlowStats current duration reports epoch milliseconds instead of elapsed job running time. It relates to this issue but only solves the case where actual Flow running times are inflated. Probably stems from the same cause though. More to follow…

[initialcontext]

We've updated this fix while correcting a separate issue, but the issue can be closed as this is fixed.