What happens after the trigger fires?
Runs, retries and the approvals queue.
01Every firing is a run
When a trigger fires, the engine walks the graph 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 does not quietly retry itself. The one exception is Send to integration, whose failures are honestly transient: it retries three times, waiting one minute, then five, then fifteen, and each attempt is claimed before it runs so the same payload is never delivered twice. Everything else stops and says so — a second email is a second email, and repeating a step that changed something real is worse than reporting the failure.
03Approvals park the run
An Approval control holds the run until a person decides. Pending approvals collect in the Approvals queue on the Flows header, with the count on the button, and approving or declining resumes the branch from where it stopped. The queue is for people who can write items, and it updates itself as others clear it.
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.