Issue with Workflow Order – Custom Events Executing Out of Sequence

[dcamorrag]

The video with the asked steps.

I’m also showing logs:

[ademiguel]

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.

[dcamorrag]

@ademiguel

@achen2222

create your 3 workflows and have them each return a value

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.

Okay, I’ll try to do that way. Could you explain a little bit more detailed? Or which is the diference between “achen2222” solution and the one I’m using?

PD: sorry for the late reply.

[ademiguel]

What you are currently doing:

• Verificar solapadas is called from Verificar duplicados
• Crear Sesion NP is called from Verificar solapadas

What it’s being suggested:

• Click on button calls
  • Verificar duplicados. Terminate if returned value is true.
  • Verificar solapadas. Terminate if returned value is true.
  • Crear Sesion NP.

[moabe.leite]

I rather repeat the workflow on button depending on the condition than create a workflow that runs e certain conditions.

Repeat the same click button action 3 times, and each times run in certain conditions, so bubble will run directly each workflow depending on the button condition action.

Because bubble always create new things first, this is native behavior from the platform.