I’m working on a custom event, and I find it a bit strange that data actions execute on a different thread.
This is causing issues because I want to evaluate a condition using the alert count from the database before creating a new one, so that a different message appears when the same custom action is run again; however, “Step 4” is the one that always executes.
It appears the “Create a New” action runs first or on a separate thread, causing the logic to fail when the condition is evaluated.
It’s quite odd; from a UI/UX perspective, you’d expect sequential execution since they are labeled as “steps,” but the actual execution flow doesn’t follow that pattern.
I would like some help figuring out how to achieve my goal.
I only ever read them when something doesn’t work as expected, or I spot a new feature in the editor and click see reference. Unfortunately new features are not always in the manual and manual no longer supports scroll to section based on click of see reference.
For example, when workflow is running condition is not in manual. @fede.bubble did I overlook the section or is it not in the manual yet? And where is the event trigger for element workflow is completed? Would be great companion to the new exposed state of element workflow is running.