How to Disable Backend Workflows

I’m putting together a series of backend workflows and database trigger changes that I need to turn off so that I can update existing database entries prior to allowing the backend workflows to run as required for all new incoming data.

Since there is not ‘disable workflow’ checkbox, I decided to add a terminate workflow action with a condition based on an option set. This was used mostly for the database trigger changes because on those triggers the only conditions we can create use the ‘thing now’ or ‘thing before change’ and we are unable to access any other data source.

Screen Shot 2024-09-27 at 11.19.32 PM
Screen Shot 2024-09-27 at 11.19.45 PM

The simple approach is all I needed so all of them use the same single option value, however, if you wanted to implement for each backend workflow you can create an option set with the display values equal to your backend workflow names, add an attribute that is a yes/no field and reference that attribute value, so you can have control over each individual backend workflow.

4 Likes

That’s clever!

I wish Bubble would implement some sort of environment variable or feature flag. And simple cron jobs so less hacks and orchestration is required to do simple, routine stuff like this.

1 Like