tl:dr - it was always broken. Got fixed a bit over time. Nothing sudden. But still could break in rare situations. But that is complex systems for you.
We need to start at the beginning …
Backend workflows have always been broken. Or rather “inconsistent”. There was an item on the roadmap “Workflow consistency” for a long time for just this reason. I have bugs that predate the bug reporting system on this
A change was made to serialise them a lot more, can’t remember when but it was before “releases”.
In the meantime changes have been made to move back to being parallel without making the situation worse. There was the “Batching steps that update the same thing” recently.
The point is, and this has been mentioned above, this is art not science. Workflow steps could run in serial, but that would be the wrong thing to do 99% of the time.
OK, I need to check my privilege here, I grew up (in Bubble terms) with things like back end workflows.
So maybe I just naturally do things “the right way”? But I don’t think that is the only reason that I don’t find that many (or indeed any) consistency issues with Bubble workflows.
One project I work on can have multi-step, multi thread, backend APIs. If something that we created 5 minutes ago fails to get into the database (so I can’t then search for it) then my problems are a lot lot bigger than just that insert.
Context - in the last months we have created over 300,000 rows of data from a complex set of API calls and backend recursive workflows.
No of problems due to Bubble Order of Operation = 0
No of problems due to me =