Question

Workflow Reporting End Time & Time of Last Action as Being Before Start Time

Workflow

Updated June 20, 2017

asked on June 14, 2017

All of the workflows for a particular server are showing that they started roughly 2 minutes after they completed and thus show a duration of 0ms.

Additionally, if I go into the workflows they show the End Time being before the Start Time, show the duration in the bar graph wrong, but do show the activity duration correctly.

If I go to the activities they show the correct durations but seem to match up more with the End Time than the start time.

Oddly enough they have another server running workflow and it is functioning properly. They are both running 10.0.0.249. Has anyone seen this issue before?

0 0

Answer

SELECTED ANSWER

replied on June 20, 2017

Yes, a little bit. It was done for efficiency purposes to eliminate a call back to get the time.

0 0

Replies

replied on June 14, 2017

Is the SQL Server on a different machine?

0 0

View 1 previous reply

replied on June 15, 2017

Sounds like the internal clock of one of them is drifting.

0 0

replied on June 20, 2017

So if I understand correctly, for the start time it pulls the time from one server and for the end time and activity times it pulls it from a different server (if SQL and Workflow are installed on different servers). While I agree the servers should be syncing up with the correct time it seems odd that Workflow would pull it's times from two different locations while processing.

0 0

SELECTED ANSWER

replied on June 20, 2017

Yes, a little bit. It was done for efficiency purposes to eliminate a call back to get the time.

0 0

You are not allowed to follow up in this post.

Question

Question

Workflow Reporting End Time & Time of Last Action as Being Before Start Time

Answer

Replies

Sign in to reply to this post.