Retry recovery and durable run history now point to different definitions of one completed run.
Fast recovery protects freshness, while a permanent identity choice protects the integrity of retained run history.
Who you’d be doing this for
“Our morning report doubled yesterday, and now leadership wants to know which table we can trust.”
Chrysanthi Serrano · Data Engineering Manager
Leads an enterprise data team whose warehouse tables feed scheduled operational reporting.
What is at stake
Duplicate completed runs are loading the same batch twice into customer warehouses. You must weigh retry recovery against a permanent definition of a completed run.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- retry recovery vs durable run identity
- warehouse freshness vs duplicate-load safety
- shared abstraction vs immediate containment
- release timing vs migration certainty
Why Fivetran
Managed ELT customers depend on completed-run records to know whether warehouse data is safe to use.
Written with these in mind
Not your kind of problem? 43 more at Fivetran, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.