Has anyone ran in to this issue before and if so, how did you solve it?
I have a pretty simple workflow that i use as my sleep timer in my workflows:
'Set date' just creates a date object that is the specified wait time seconds in to the future and then calls 'Waiting timer' with that date.
It seems to work great, the workflows suspend like they should, reducing the load on the server while its waiting for the next thing to do.
However, if the server is restarted and the workflows resume afterwards the 'Waiting timer' never seems to trigger. I'm guessing this is because the time it is waiting for is actually in the past.
Anyone know of a way to solve this or a better way to suspend the workflows without using System.sleep()?
Accepted Solutions
Ok, so it looks like its a issue with 5.1.0 build 2725. I'm not sure at what point it was fixed, but it is working in 5.5.1 build 1617127.
The issue is that 'Waiting timer' does not throw an exception if the date it is waiting for is in the past, in 5.5.1 it does.
I changed the workflow to gracefully handle the case where the vCO server is restarted while Waiting timer is suspended.
Ok, so it looks like its a issue with 5.1.0 build 2725. I'm not sure at what point it was fixed, but it is working in 5.5.1 build 1617127.
The issue is that 'Waiting timer' does not throw an exception if the date it is waiting for is in the past, in 5.5.1 it does.
I changed the workflow to gracefully handle the case where the vCO server is restarted while Waiting timer is suspended.