Help with moving the workflow beyond a long timer

[dp11]

Hi,

I have a timer activity in a WF which I configured mistakenly to 3 days (72 working hrs) instead of the needed 3 business days (27 working hrs). Our user has submitted several items and they all are now stuck at the timer for a much longer period than desired. There is a catalog task that needs to be created after the timer ends. 

I have been experimenting on our Dev instance for ways to get the WF to move beyond the long timer activity but haven't had any success. 

Has anyone ever helped themselves out of such a situation?

Thanks,

Deb

[GoBucks · Accepted solution]

@dp11- I have discovered one manual method that can move a timer activity to finish ahead of the set time it would otherwise finish at, and therefore move the workflow along to its next activity sooner as well.

Once the workflow initially moves to the Timer activity the Workflow Context diagram will show the Timer activity as being in a State of 'Running' (green), AND a record gets created in the sys_trigger table at this time.  This sys_trigger record is named "Workflow[sys_id]"  where [sys_id] is the sys_id of the running workflow context record.  Example:

Notice on the above image that this record contains a date/time field named "Next action".  An admin can edit Next action value to be something that occurs within the next few minutes (or whenever) and save the record.  When that moment in time comes to pass the sys_trigger record fires an event that moves the workflow along from that current timer activity to the following activity.

[Mark Roethof]

Hi there,

Here you go:

- 2020-11-30 - Article - Speed up Workflow testing on "Timer" utility

Kind regards,
Mark