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.
intermediate
6:42
Read a run history and fix a broken mapping
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.
Video placeholder
A run history table with a column of failed rows, one row expanded to show a side by side read and write panel. The read panel has a value, the write panel is empty and outlined in amber. A replay button in the corner.
Chapters
From the transcript
Somebody says the flow is broken. It usually is not broken. One record is failing over and over, and the run history will tell you which one in about thirty seconds. Open the flow, open History, sort by failed. Here we go, the same error forty one times since Tuesday. Property Priority does not exist. Now, the useful part of this screen is not the red text. It is the two columns beside it: what we read from Notion, and what we tried to write to Trello. Read side shows Priority with a value of High. Write side shows nothing, because somebody renamed that property in Notion on Tuesday morning and the mapping still points at the old name. So I fix the mapping, I hit replay on the failed runs, and all forty one go through in one pass. Replay uses the record as it exists now, not as it was on Tuesday, which is what you want almost every time.
More videos
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.