Hello all,
I’m newbie using bubble.
I don’t understand the way works the workflow I’ve created.
On the event click of a button, I check unity of the data before creating it in database.
I’ve a few steps before the step CREATE DATA.
BUT when I’m using the debugger, at the first step the data is allready created far before the step containing the CREATE DATA.
I’m turning mad with that comportment, Could someone explain me what’ I’m doing wrong ?
Thanks a lot for your precious help.
You’re probably not doing anything wrong. The issue (and what drives many people crazy) is that Bubble workflows don’t always run in the order you build them. Yes, it doesn’t make sense, but that’s how it works. And sometimes this causes logical issues. Workflows run asynchronously, but there are ways to force them to respect a specific order.
Could you share your workflow (and the problems you’re running into with it) so we can help you organize it correctly?
1 Like
Hi! It sounds like your workflow might be triggering the “Create Data” step earlier than you expect, which usually happens if you’re using “Make changes to a thing” or “Schedule workflow” actions before the actual Create step, or if there’s a workflow running on page load that creates the data automatically.
Make sure the “Create a thing” step is the first action that actually creates data, and check that no “Make changes to a thing” actions or other workflows are running before it. Using the debugger step by step and temporarily disabling other actions can help you see what’s happening.
Hope this helps! Keep experimenting, Bubble can be tricky at first but gets easier.
1 Like
Many thanks for helping !
Here is my workflow 
I just added pause actions between steps but It doesn’t change any thing.
As you can see, I’ve put the functional events in Custom Events.
Account_already_exists to check unicity
Nbmax_membres_atteint to check a counter
And finally Create_membre to insert data in database.
When I use the debugger, at first step (Bton_inscription2 is clicked) the Data Entry membre is created, before controls 
Can you explain why the action of create a new member, beeing triggered first, is resulting in some issues?
Becausa I noticed that you already inserted conditions in the “Only When” field of your Step 7, that will prevent you to create duplicated records…
The pause action also does not impact database activities.
1 Like
It’s an issue because step 3 and 5 are controls to verify unicity of the new member.
Creating the Member before controling its unicity is totally unconsistant.
Is there just a simple way to play steps in order I wish them to do ?
I have removed the pause steps (that are unconsistent) and i ran my workflow again
Juste after clicking the button the debugger shoes the first step of my workflow:
But as you can see below, the data type Membre is created much early as I expect it :
I am looking for a solution that simply performs the workflow in the order I expect.
Thanks
But what exactly are you doing inside that Custom Event that checks for unicity? Why don’t you place that validation directly in the Only When field of the event that creates the record?
Your step 7 (which is the one that creates the new member) doesn’t depend on any previous step. That’s why Bubble is processing it immediately. If the creation of this new member needs to depend on previous steps, you must condition that somehow.
I’m turning mad with that workflow…
Well, let’s keep it simple. Here is what I have done to simplify the test, but still got the same issue.
I just add a new button on my page, that calls the following worflow when it is clicked:
My page looks like this just before clicking:
The counter (id #1) is the do search that’s in the only when of the CE Create_Membre
My button for the tests is the one red-ringed.
The I click on “valider form test” and here is the first step of debugging mode:
As you can see, the counter has changed to “1” BUT I did not see the debugger pass in the Trigger Create_member.
The data entry has been created as I didn’t expect it to be:
I don’t understand what’s wrong !
Many thanks to you
I went through a similar issue once. Even when splitting my workflows into “custom events,” they were still being executed out of order, specifically one that involved “Create a thing.”
I understand that what’s bothering you is that the workflow is being executed earlier than it should. But the important thing is to understand what problems this is actually causing you, because I see that the unicity is already being checked in the “Only When” field. Is there anything else you need to validate or wait for before creating this new member?
Working with Bubble is like that. Sometimes the best path isn’t a straight line.
My bad !!!
I was misled because it appears that the database is updated before the debugging steps are carried out. That troubled me!
It seems now to process as i expect it
Even if I find the way to proceed not “natural” because in theory you do the unicity check before creating elements, playing with “only when” seems to meet my needs.
I have to change my way of thinking, I Thank you for your really precious help !
1 Like
Yes, this is correct. The debugger is not helpful in situations like this unfortunately.
1 Like