Context:
I need to run a number of workflows sequentially ensuring that the next one only starts after the previous has finished.
I’ve implemented a WFLoop thing that contains a start and end times - the end time is set empty when it starts and then filled with current time when finished.
From front, I use the Trigger custom event when data changes to listen to the field endTime changes in order to take action and start the next workflow.
Problem:
Trigger custom event when data changes is behaving erratically: sometimes goes through all events (may reach up to 11 workflows) and sometimes just stops in the middle although the endTime was set in DB.
Anyone has come across this problem?
Is Trigger custom event when data changes not reliable?
If the workflow is only intermittently starting, it’ll be this.
If the workflow always starts but sometimes stops in the middle, that’ll be some other issue, for which you need to share more details of the workflow.
Hi @alan8
The heaviest workflow may handle 2000 records at most - this shouldn’t be a problem.
Hi @georgecollier
None of the workflows stops in the middle, it is the chain of workflows that is interrupted because front doesn’t detect that endTime for a workflow was updated and, therefore, it doesn’t call the next one in the chain.
Hi @alan8
According to the post @georgecollier indicated, this problem occurs in live version, not in dev.
So, I’ll give it a try testing in dev version first to check if it is the same problem and I’ll let you know what the result is.
Thanks anyway,