What happens after the trigger fires?
Runs, failures and approvals on the card.
01Every firing is a run
When a trigger fires, the engine walks the rail and records a run with one step per node it touched. Runs opens that history for the selected flow, newest first, so you can see exactly which branch a particular booking took and where it stopped.
02When a step fails
A failed step never quietly retries itself: a second email is a second email, and repeating a step that changed something real is worse than reporting the failure. The step’s failure route decides what happens instead: nothing, or a move to a stage you named.
03Approvals live on the card
An Approval step holds the run until a person decides, and the ask sits on the item’s own card at that stage. Approve or decline resumes the branch from where it stopped; the first decision wins and stands.
04Waits
A Wait control holds the run for a set duration or until a date on the item. Nothing is lost while it waits. The run is parked and picked up again when its time arrives.