Workflow step is empty meaning

I have a backend workflow with a few steps.
The first step makes changes to an element if conditions are met and it changes this element field Y to value X which may or may not exist (it is based on a another search ).

If I in the next step refer that this step is empty - I get information that:
a) This step was executed and the value it assigned was empty/null.
b) This step wasn’t executed as the conditions were not met.

I assume it’s case b) right?

Could it also be that the two actions are executed simultaneously and the second action executes before the first one has completed?

It can be possible, but I just want to link them in a proper way. As if one action has a condition to use step 1 result it waits for the step to finish. But I just wander what does it mean - step is empty. It means it didn’t trigger or it means it assigned a null value as well.

From my experience, it either means that the action didn’t execute because of following:

  1. Condition in the step didn’t meet and hence step was not executed
  2. The action failed due to some connection issue etc e.g. Schedule API workflow didn’t happen because of capacity issue
  3. The object that the change was to be made to (make changes to a thing) was done on object that was empty e.g. If the object to change was result of search for and it resulted empty

This has nothing to do with the value you assigned to a field to a thing.

This is just my experience and understanding. I don’t think this is well documented.

2 Likes

Thanks @mghatiya.
Thanks everybody!