Sometimes code processes multiple things in parallel, aka asynchronously, often applied by something like async.
When the multiple things have no dependency on each other, no problem! This lets everything move along at full capacity instead of piling up behind the slowest thing.
When the multiple things do have a dependency on each other, the uncontrolled order of operations can cause variable results or errors. Step 2 might require the output of step 1, which seems intuitive when phrased that way, but sometimes Step 3 sneakily requires the output of Operation F and it’s not so obvious.
Inserting a serial (aka sequential) action between a couple of async things can break their async relationship and force them to run sequentially. When something like that changes how the before and after steps work, that’s a good first place to look. Not anything we can look at though, someone up the developer food chain would need to do that.
So, backstory: each of those mini-events has just a single action (row-update or property-set), and I used to have them NOT in their own events, and I tried the “Success” arrows, but that kept bombing. Tried Conditions also.
FYI - I assumed you also wanted me to remove the slide-out message… otherwise what would I be testing?
It may help to know the context, which is the loading input data from the app-open (these screenshots are from the app that gets opened). I feel like there is some major voodoo there.
