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.

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.