I believe the whole point of the “Terminate this workflow” action is to interrupt a synchronous workflow. Why do we have the “Terminate this workflow” action available in backend workflows if backend workflows are not going to evaluate it synchronously?
If this is the case, I believe this must be fixed ASAP. My suggestion would be:
If there is a “Terminate this workflow” action present in a backend workflow, evaluate it synchronously. Or even better, let us choose when to evaluate any workflow synchronously or asynch (vote for this feature here).
“Since backend workflows do not operate synchronously, actions placed after the ‘Terminate this workflow’ action may execute before the termination occurs.” That’s what I mean by being ignored.
It is not a common thing to experience. After 5 years of building in Bubble I think I’ve only experienced or noticed it today.
I hope I’m wrong.
Please let me know if I am, thanks.
So backend workflows are not evaluated synchronously, except if there is a “Terminate this workflow” action?
In that case, conditions in the backend workflow would always be evaluated synchronously, ensuring nothing after the Terminate this workflow gets triggered if the workflow is terminated by that action?
If there is a terminate this workflow action and it’s condition passes then no steps positioned after the terminate this workflow action will run. That is the expected behavior.
The other action that behaviors similarly is “trigger a custom event” - it will complete all actions within the custom event itself before returning to the triggering workflow and then continuing with the subsequent actions there.
That’s how I’ve worked with it for 5 years, but today I experienced something different. It occurred during the time that some issues with the main Bubble cluster were detected, so it might have been a related bug.
