Issue with Workflow Order – Custom Events Executing Out of Sequence

javier6 · 2025-04-01T19:25:38.354Z

I’d recommend going through the debugger step-by-step and checking those conditions which are failing to trigger the terminate action

dcamorrag · 2025-04-02T14:49:47.519Z

I didn’t know about the “Terminate this Workflow” behaivour. Thank you.

The conditions are not the problem. They behave as expected if I delete de CE “Create Session NP”. The problem is that the session is created before anything else, and it makes everything to fail.

Debugging step by step everything follows the woorkflow as it should, but the problem is that as the session is created at first (for some reason I don’t know).

May it be a bug?

dcamorrag · 2025-04-02T14:50:53.175Z

The problem is that as the session is being created at the beggining (I don’t know why) it triggers the ‘wrong’ conditions.

javier6 · 2025-04-02T15:16:56.157Z

Workflow actions on the front-end shouldn’t run asynchronously so I don’t think that’s the problem.

What are the search parameters on this action? It could be that this action is failing to set it to yes

Search for Sessions:count is 0

If I understand, you have the same condition here, it could be either your Search for Sessions:count is 0 is not set up properly, or your Group Widget Nueva sesion NP's Crear Sesion is yes is actually no

image346×132 23.6 KB

I did find a useful thread here

Order of Operation Need help

Hey there, thanks for posting! If you’re interested in Order of Operations, you might check out this section of our Custom States tutorial: How to Use Custom States | Bubble Tutorial - YouTube Then, here is some information about Bubble workflow logic: For efficiency purposes, workflows run in parallel across the server and the front end. Despite the names “Step 1”, “Step 2”, it is important to note that a given step does not necessarily wait for the previous one to complete before triggering …

Order of Operation

Custom events run in sequence, not parallel. If Workflow 1 triggers a custom event that starts Workflow 2, Workflow 2 will complete before the remaining actions in Workflow 1 run.

It seems like there might be a race condition in your logic, but I wouldn’t know unless we dug deeper into the workflows and debugger / logs.

ademiguel · 2025-04-02T15:25:02.373Z

Weird thing. What should these Verificar Duplicados and Verificar Solapadas CEs conditions evaluate to when the bug happens? True or false?

Only when Search for Sesions:count > 0
Only when Search for Sesions:count is 0

dcamorrag · 2025-04-02T17:43:17.633Z

Hi! Thanks for taking your time and answer.

The ‘Set State’ is not changing nothing, actually. If I delete it, it will run the same way. I just put it in order to add another conditional, but it does not works.

The problem is when there is the action “Create a Session”. When I put it, it will be created before anything else.

I’ll try to post a video so you guys can see.

dcamorrag · 2025-04-02T17:56:23.701Z

Only when Search for Sesions:count > 0 is the condition that detects duplicates. If there is another session that has the same information as the one that is being created, then shows an alert and should end the workflow (or in that case, should not pass to the next CE).

Right now, when the bug happens it is evaluating:
Only when Search for Sesions:count > 0 as True
and
Only when Search for Sesions:count is 0 as False, but just from the CEVerificar Duplicados, because once evaluates it as False, the Workflow ends.

In order to create the session:
The Only when Search for Sesions:count > 0 condition from both CE should be False
and
The Only when Search for Sesions:count is 0 condition from both CE should be True.

ademiguel · 2025-04-02T18:08:29.275Z

In order to verify we are dealing with a bug, try placing a couple Text elements on screen that show the results of both conditionals, with exact same constraints for the Search for expressions.

If they return this below, and the Sesion gets created, we are seeing a normal behaviour, no bug.

dcamorrag:

The Only when Search for Sesions:count > 0 condition from both CE should be False
and
The Only when Search for Sesions:count is 0 condition from both CE should be True.

If we see this, and the Sesion gets created, then it’s a bug.

dcamorrag:

Only when Search for Sesions:count > 0 as True
and
Only when Search for Sesions:count is 0 as False, but just from the CEVerificar Duplicados, because once evaluates it as False, the Workflow ends.

dcamorrag · 2025-04-02T18:10:18.817Z

Video where you can see the Step by Step and the premature creation of the session.

dcamorrag · 2025-04-02T18:17:11.161Z

Sorry, but I did not understand exactly how to do that.

In case it is useful, I did a video where you can see how the session is created before anything else. If not, could you explain me exactly what to do, please? Thanks!

Video - Step by Step and the premature creation of the session.

javier6 · 2025-04-02T18:20:13.686Z

Definitely looks odd, I would go back through your server logs from 3:00-3:02 and see what action triggered to create the item in the DB, it could be firing from another action that’s not included in your custom event, otherwise it might be a bug.

ademiguel · 2025-04-02T18:26:45.698Z

This is a weird behaviour of the debugger, I’ve seen it before.

But I see no bug in your execution, the Sesion gets created because there is no duplicated Sesion in DB.

If you try executing it again an a second exact Sesion gets created, then it’s a bug.

dcamorrag · 2025-04-02T18:30:11.973Z

But that weird execution is triggering the alerts. Then when someone is creating a session, always will appear the alert “That session was not created because is a duplicate”.

How can I solve it?

ademiguel · 2025-04-02T18:31:12.779Z

Try executing it without the debugger, just as a normal user would do.

Let’s see if the bug is present then.

dcamorrag · 2025-04-02T19:00:08.738Z

I looked and I think there’s something weird. I am not used to look at the logs, but it starts with the “terminate this workflow” conditions:

Log 1/31600×624 68.2 KB

Log 2/31600×527 55.2 KB

Log 3/31600×439 41.3 KB

dcamorrag · 2025-04-02T19:01:32.294Z

Same problem running normal.

ademiguel · 2025-04-02T20:53:04.531Z

Please record another video, running without the debugger active, showing the next steps:

Show DB table for Sesion
Click the button. It should run without alert being shown. Sesion should get created.
Show DB table for Sesion again. The newly createdSesion should be there.
Click the button again (I guess this will try to create a duplicated session). The alert should show now. No new Sesion should be created.
Show DB table for Sesion again. No newSesion should be there.

If what’s described in previous steps don’t happen as expected, show logs

achen2222 · 2025-04-02T21:21:51.808Z

from a programming point of view instead of nesting your workflows like that, create your 3 workflows and have them each return a value (return a value step is hard to find so just type return when you are creating the step).

have the top level work flow call the first one (which will have a value) then the second one only if the first step condition was met. Then the third one only of the original conditions are met.

In general your custom event should take parameters and return values rather than pulling in information from all over the place. This keeps the workflow tidy and allows you to test it more easily.

dcamorrag · 2025-04-02T21:44:07.789Z

The video with the asked steps.

I’m also showing logs:

ademiguel · 2025-04-03T07:51:31.669Z

Gotcha.

The behaviour you are experiencing is something expected. Bubble tries to, counterintuitively, execute in parallel all actions in a workflow unless:

An action refers to a previous action result, with a Result of Step n expression. In this case, the second action will wait for the first one to complete. It does not affect the rest of actions, that will continue executing in parallel.
An action is placed after a CE. In this case the action will wait for the CE to complete.
An action has a conditional that evaluates to false, so the action isn’t run.

Since 1) your CEs are always the last action of a workflow, 2) you have no action referring to a previous action result and 3) conditionals that lead to the execution of Create a Sesion action all evaluate to true, your flow triggers every action in the chain in parallel, including the Create a Sesion action.

When actions like those showing the alert finish executing, the Sesion record is already created, so they execute.

You will avoid this by following @achen2222 advice, since CEs will be placed one after another in the same workflow, and won’t execute before the previous CE is done.

achen2222:

create your 3 workflows and have them each return a value

achen2222:

have the top level work flow call the first one (which will have a value) then the second one only if the first step condition was met. Then the third one only of the original conditions are met.

Disclaimer

I just find weird that the Create a Sesion action is done executing before the Search for Sesion:count > 0 does, because even if all actions execute in parallel, they are initiated sequentially, and one might expect that in a long chain of actions, the first ones might be done executing before the latests.

The Search for expression might take much longer than the Create a thing, though. That might explain it, I am not sure.