{{title}}

What happens after a run goes wrong, and what happens when you point a flow at eleven thousand old rows. Which errors get retried and which never will, how a queue looks different from a failure, and the backfill settings worth checking twice.

One trigger, three actions, and the order decides whether the result is usable. A first payment creates the contact, moves the deal and opens the onboarding card, each step handing its output to the next, with a clean stop when the first one fails.

The flow is rarely broken. One record is failing over and over, and the history names it in about thirty seconds. Sort by failed, read the two columns beside the error rather than the error itself, fix the mapping, replay the backlog in one pass.