We’ve encountered an issue where one of our backend-workflows keeps repeating itself (we also understand the cause). Even after cancelling all scheduled workflows, it still keeps restarting. Our temporary solution was to delete this problematic workflow.
In our development version from yesterday, this problem did not exist in this workflow, so we’d like to revert to that version. However, if we do so, the problematic workflow will start running again because it seems that some triggers are still stored and ready to execute (even if our schedular doesn’t show anything scheduled).
We’re looking for a way to revert to an earlier version without re-triggering workflows that were initiated after that time.
In summary:
Does anyone know of a method to revert to a previous development version without triggering workflows that are already scheduled or set to run based on actions that happened after that version?
Thanks in advance for any insights!
AFAIK, there’s no way in Bubble to prevent workflows from triggering when you revert to an earlier version—anything programmed to run will still run.
To troubleshoot, I’d suggest:
- Working in a new branch to recreate the functionality you need
- Manually canceling scheduled workflows
- Disabling workflows that you don’t want triggered
thnx.
The main problem is I cant disable the workflows because they are backend workflows.
Recreating the functionality would cost a lot of time… and cancelling the scheduled workflows does not seem to work for some reason.
Is it me or is this just strange… the workload will spike and there is not a simple method to just cancel them. I understand we made a mistake and bubble cant do anything about the workload spike it created, but in my opinion they should provide a better solution to cancel all workflows scheduled after a certain date/time or give the option to disable backend workflows
Thnx again, we know about this option. But it still seems te trigger again somehow. I have only managed to get it cancelled by deleting the workflow completely… the problem is somewhere in the last step of the workflow.
I’ll take a deeper look into it.
1 Like
Hi cmarchan,
Somehow I got it cancelled this time (doing the exact same steps as before). It doesn’t trigger itself anymore so we are relieved.
Thnx, again for the quick responses!
1 Like
