Failed automation review archive context checklist: keeping run-to-repair links before the rebuild

Short answer

Work through three stages in order: before the review findings go to the client, before rebuilt workflows go live, and before old workflows, error queues and run history are cleared. At each stage confirm a few facts, name who on the client side owns them, and note what is lost if the item is skipped. The point is to keep the company's choice open: are failed runs still linked to the authorized actions that repaired them when the cleanup arrives?

Visual briefFull-size diagram
A vertical countdown with three stages, findings delivered, rebuild live and old workflows cleared, where checklist items tick green one after another and one skipped item stays orange.
Illustrative countdown. Retention marks are documented platform defaults; each client's own settings decide the real dates.

This checklist belongs to the failed automation review guide for workflow automation agencies. It invents no deadlines. Each stage is tied to the client's own event, and the retention figures quoted are documented platform defaults that the client may have changed.

Countdown to the rebuild

A failed automation review has its own rhythm: diagnose, report, rebuild, clean up. The repair history is most at risk at the end, when cleanup feels like good hygiene.

StageWhat happens to the evidenceWho sets the date
Findings deliveredFailed runs and error queues are still in place; the repairs are scattered across business systemsAgency and client sponsor
Rebuild liveNew or edited workflows replace old ones; some platforms keep history with the old workflowAgency and operations lead
Old workflows clearedDeleted workflows, emptied error queues and aged-out run history take the platform half with themClient admin

Retention keeps running underneath all three. Zapier's help says it can only promise up to 60 days of run data in Zap history. Microsoft documents that Power Automate stores flow run data for 28 days by default. Those clocks do not wait for the project plan.

Stage 1: before the review findings go to the client

Everything is still in place. The aim at this stage is to describe where the two halves of each incident live before anyone changes anything.

ConfirmWho owns itIf skipped
Which platforms are in scope and what run history retention each is set toClient admin for each platformThe 28-day or 60-day window can close before anyone asks
Whether incomplete executions are stored at all, where the platform makes it optionalScenario ownerIn Make, incomplete executions are stored only when the scenario setting is enabled, so some failures were never kept
Where human repairs are recorded: ERP or CRM change history, helpdesk tickets, email, or only as replaysOperations, finance and sales operations leadsThe repair half stays invisible and looks unrelated to any run
What key, if any, ties a repair to a run: run ID, order number, ticket numberSame leadsPairs cannot be matched later, even when both halves survive

The repair half is usually outside the automation platform entirely. An accounts receivable clerk fixing a tax code in the ERP or a controller approving an exception by email leaves a record in their own system, not in the run log.

Stage 2: before rebuilt workflows go live

Rebuilding is where history can split from the workflow it belongs to. The questions here are about what the new version inherits.

ConfirmWho owns itIf skipped
Whether rebuilt workflows are edits of the old ones or new workflows that replace themAgency build leadA replaced workflow's history may be deleted with it at cleanup
How failed runs were retried during the review: replayed unchanged, or retried after a changeAgency build lead and client adminThe difference between "pressed replay" and "fixed the cause" is lost
Whether replay is still possible for older failuresClient adminZapier notes that steps older than two months will not replay, so older failures can only be described, not retried
Whether the business-system repair records have their own retention ruleFinance or ITThe repair half may age out on a different clock from the run half

n8n shows why the second row matters: it can retry a failed execution with the original workflow or with the currently saved one, so a retry after a change leaves part of the fix in the workflow's own history. Ask how the client's team retried, and note it.

Stage 3: before old workflows, error queues and run history are cleared

This is the real deadline, and it is the client's. Cleanup is often scheduled as the final task of the project.

ConfirmWho owns itIf skipped
The date old workflows will be deleted or archivedClient adminThe platform half disappears on a day nobody chose for this reason
Whether error queues will be emptied, and whether anyone has noted counts and periods firstClient adminThe best evidence of what went wrong is removed for tidiness
Whether the owner has heard about the licensing option and who would decidePartner, with the ownerThe question is never asked
The owner's recorded choice: introduce, revisit later, or stopPartner, with the ownerThe decision is made by default when cleanup finishes

Skipped items and what they cost

Illustrative. A 270-person industrial supplies distributor ran a review of its order-to-cash automations across two platforms.

ItemWhat happenedEffect on run-to-repair pairs
Retention settings noted at stage 1Done; one platform at its default window, one extended by the clientRecent pairs intact on both platforms
Repair key identifiedDone; order numbers appear in ERP comments for about half of repairsRoughly half the pairs can be matched
Rebuild approachSkipped; three workflows were replaced rather than editedTheir history went with the old workflows at cleanup
Owner decisionRecorded before cleanup: revisit after the next quarterThe choice stayed with the owner

A partial result is normal. The checklist turned an accident into a decision. The guide on assessing human review records and correction workflows explains why matched error, correction and outcome sequences matter, and why AI agents fail covers the same pattern from the agent side.

Fit and authority check

The client company usually owns its business-system records; the agency only holds delegated access to the automation platform. Customer contracts and privacy rules may limit reuse, which the company's counsel decides. The person who can authorize a licensing discussion is the CEO, who in an owner-run company is usually the owner.

Check fit before any introduction: 50+ full-time employees at peak (contractors excluded), a documented operating history, rights to license the records, and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

Stay at metadata level: platforms, periods, rough counts, where repairs live, who owns them. Do not export run logs or Zap history to show SourceX what exists. What stays unknown until SourceX reviews it: demand for these records, the rights review result, de-identification needs and any offer. Sign the Channel Partner Agreement before submitting; attribution goes to the first valid introduction within the 90-day window, credited when the company submits a verified application. Illustrative only: a USD 100,000 Actual Supplier Payout to the company would mean a USD 55,000 reward under the rewards page conditions. When the owner opts in, the failed automation review introduction email is the next document. For accounting automations specifically, see MCP journal entry automation, and for the platform contrast, the MCP vs Zapier explainer.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If stage 3 is still ahead, the run-to-repair links hold, and the owner wants to talk before cleanup, register as a partner, confirm the company on who qualifies, and read the program terms first.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

Should the agency export run history to protect it?

Not as a referral step. Whether to export or retain run history is the client's own decision, made by its admin under its own policies. The partner's job is to make sure the question is asked, not to collect anything.

What if the client's error queues were already cleared last year?

Then the platform half is gone for that period, and the checklist records that. The repair half may still exist in the ERP, CRM or helpdesk, keyed by order or ticket number, so the later rows still matter.

Is this checklist only for Zapier, Make, Power Automate and n8n?

No. Those are the platforms with documented defaults cited here. Any workflow tool raises the same three questions: how long runs are kept, where repairs are recorded, and what cleanup removes.

Sources

  1. refer.sourcex.si/terms
  2. help.zapier.com/hc/en-us/articles/8496291148685-View-and-man…
  3. zapier.com/help/manage/history/replay-failed-zap-runs
  4. learn.microsoft.com/en-us/troubleshoot/power-platform/power-auto…
  5. help.make.com/manage-incomplete-executions
  6. docs.n8n.io/workflows/executions/single-workflow-executions

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment