Do backend workflows run in order now instead of immediately?

Questions
1

It’s always been the case that backend workflows actions run immediately no matter their order in a front end workflow, or so I thought. I have a workflow that increments a custom state number by 1, and the schedule API workflow action is dependent on this number. Weirdly if I move the “schedule api workflow” action to the bottom of the workflow, it won’t run (because the number doesn’t meet the condition). But if I move it to the top of the workflow, it runs before the custom state increments.

Also, there is a slight “lag” or delay when the schedule api workflow action runs before the other steps. Is this new behavior? A bug?

2

Actions run as soon as all of their dependencies are available, though if you’re using Do a search for X rather than result of step Y, then the search may not have updated with the earlier value etc