During BubbleCon 2024 the team announced and demoed new workflow designs and features.
Please add all your thoughts, comments, screenshots and feedback in this discussion thread to make it easier for the team to ingest and review.
Thanks!
PS: I will merge some of the existing comments into this discussion thread as I find them
Hey Bubblers,
Iāve been exploring the new workflow design in Bubble, and Iād love to hear your thoughts! Itās cleaner and more intuitive, but Iām curiousādoes it actually improve your workflow speed?
UI changes : Smoother look, but is it more efficient for you?
Action visibility : Do you like the improved layout, or miss the old one?
Learning curve : Easy to adapt, or are there some challenges?
Howās the switch for you so far? Letās chat below! 
@fede.bubble maybe a thread like this should be under the announcements?
Thoughts and feedback:
flow at the end of each workflowās nameIām still gathering some thoughts and testing it, but Iām going to be honest, overall Iām not vibing it at the moment. Quite clunky and cumbersome, I feel like its more āalphaā than ābetaā.
Comparing to some of the screens on bubble con, missing features like workflow events grouped by type would be super useful to find things in large sets of wfās. Maybe Iām still adjusting, but there is some really low hanging fruit where things can be improved and as others have spotted, some bugs that need addressing.
100% agree with @rico.trevisan, this needs its dedicated thread and can also serve as an on-going place for improvements, issues and whats to come in this spaceā¦
What a great update to the workflow editor! I created different folders to better organize my workflows. However, a workflow can only belong to one folder, and I have many workflows that are part of multiple scenarios (folders), especially in the backend workflows. Will there be an option to label workflows so I can create scenarios and add the relevant workflows to each one? This gives a better overview of the flow of an senario.
i donāt see how i can use these folders for every senario? now i created the folders:
Clicking on Go to API takes you to the Backend workflows page but it sets the active tab to the design tab which doesnāt exist in the backend workflow.
Please let us revert back to the old system even though we donāt have admin rights of the editor! Seems like an oversight that could be patched quite quickly.
I might need to contact a client just to make them uncheck the advanced feature, which is not ideal. And without being able to switch back and forth iād probably simply end up not using it on client apps.
Hey guys, 
Iāve been exploring the new Workflows design, but I still canāt find the way to create ābranchesā in the conditions. Does anyone know if this has not been released yet or how I can make the conditions this way?
This has not been released ā this was a ālooking forwardā statement that was more ānow that weāve cleaned up the UX, it lays the groundwork to do stuff like thisā
Hello, its posible to turn off the beta testing and back to the normal version? im not ready yet to change at the new UI. Help!
This will work - but only if you have admin collaborator rights on the appās editor.
Itās more intuitive but itās not going to change much about workflows in Bubble until their conditional branching, looping, and parallel processing options come out IMO.
I know there are ways to loop with Bubble, but none of them are performant. Whenever I need to create a list of things I still use n8n to do it.
This is really great I hope to see the loops soon, mostly for front-end processing. There are 2 main elements missing that would be really critical to see in order to better design workflows ;
Does anyone know if the new workflow editor now runs each step synchronously? Seams a bit weird if it is asynchronous if they name them STEP 1 etc.
I havenāt looked at it in too much detailā¦ but I would assume thereās no change in how workflow steps runā¦ this is just a change in the editor as far as I can tell.
This is correct
which is super strangeā¦ we have to agreeā¦
the new design of the workflow tab and the future updates with loops, conditionals, etc. lead us to believe that the steps will be respected. Making the workflows run synchronously is crucial to ensure accuracy in the processes that are being triggered.
New users will continue to think that their flows are broken or that the platform is presenting some bug.
They could even make an option, like the javascript plugin itself has, to mark whether we want the action to run synchronously or not. There would be no problem. But it should be a userās premise.
Since long back people have been talking of how counter intuitive the āstepsā in workflows are. I even had an ideaboard item for this.
Finally they work on all that and retain that confusion. 
