The AI data opportunity inside abandoned workflow automations

Short answer

The records that connect a failed automation to its human repair are the failed run itself (its time, the step that broke and the error), the record the run was handling (an order, invoice or ticket number), and the human trail that followed: a support ticket, a manual tracker, and audit entries showing a person completing the work by hand. When those share a key such as an order number, the failure and the fix can be read as one sequence.

Visual briefFull-size diagram
Two-lane timeline: an automation lane where runs succeed, then error, then the automation is switched off, and a people lane where staff rekey orders by hand; dashed links join each errored run to the manual entry through the order number.
Illustrative timeline at a fictional food distributor. The order number is the key that joins the two lanes.

What records connect a failed automation to the human action that repaired it?

Three groups of records, joined by one key. Without the key, they are three unrelated piles.

RecordTypical systemWhat it showsJoin keySurvival risk
Failed runAutomation platform run historyWhen it failed, which step, the errorThe item it was processingShort retention; lost if the automation is deleted
Item recordERP, CRM or helpdeskThe order or case the run should have handledOrder or case numberUsually kept for years
Manual trackerShared spreadsheet or listWhich items staff handled by hand, by whomOrder number in a columnOften overwritten or archived informally
Fix ticketIT or operations ticketingDiagnosis, decision to repair or retireAutomation name, error textKept, but rarely linked to items
Audit entriesSystem people typed intoThat a person, not the integration, created the recordRecord ID and userDepends on whether auditing was on

Run history is the fragile part. Microsoft's documentation for Power Automate points users to a 28-day run history to find a failed run, where the failed step is marked and its error shown. Zapier documents run statuses such as Errored, On hold and Safely halted, and requires errored steps to be replayed within 60 days of the original trigger event. It also notes that failed runs cannot be replayed once the Zap has been significantly changed. In both cases, the detail of a failure is easiest to capture while it is recent.

An abandoned automation, week by week (Illustrative)

A fictional 170-person specialty food distributor built an automation that copied web-shop orders into its ERP. Here is what happened, and which record each event left behind.

  1. Week 0. The automation runs cleanly. Run history shows successful runs, one per order.
  2. Week 1. The web shop changes its order format. Runs start failing at the step that maps product codes. Each failed run records the order number it was processing.
  3. Weeks 1 to 6. Customer service rekeys orders into the ERP by hand. A shared spreadsheet lists each order number, who entered it and any corrections. The ERP's audit trail shows those orders created by named staff, not by the integration user.
  4. Week 3. An IT ticket records the diagnosis: the product code field moved. Fixing it needs a developer the company does not have.
  5. Week 6. Operations decides to switch the automation off. The manual process, with its spreadsheet, becomes standard.
  6. Month 5. A new integration replaces it. The old automation is deleted, and with it, its run history.

Events 2 and 3 are the valuable pair: a machine failing on a specific order, and a person completing the same order correctly, with corrections noted. Event 6 is why timing matters. If nobody exported the run history before deletion, only the human side remains.

Ownership: the question that stops most conversations

Abandoned automations are often owned by nobody in particular. The person who built one may have left, and the account it runs under may be theirs.

That has practical consequences. Microsoft notes that in Power Automate's automation center, seeing a flow's run history requires being its owner, co-ownership not being enough, or having environment-wide access. So the first question is not "what is in the runs?" but "who can still see them, and who owns the process today?"

For an introduction, establish at metadata level:

  • Which platforms ran automations for the process, and roughly when they were built, failed and retired.
  • Who owns the process now, usually an operations, finance or customer service manager.
  • Whether run history still exists, or only the human side (tickets, trackers, audit entries).
  • What key links them: an order, invoice or case number present in both the failed run and the manual record.
  • Whose data it is. Orders from the company's own customers are usually the company's records. Automations run on behalf of clients may belong to the client.
  • Who can authorize a licensing discussion: the CEO, usually the owner in an owner-run company.

The company also needs 50 or more full-time employees at peak (contractors excluded), a documented operating history, rights to license, 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. See who qualifies.

Why the human side carries the value

An automation's success records show the easy path. Its failure records show where the easy path broke. The human records show what a capable person did instead, including the corrections they made along the way, such as a discontinued product swapped for its replacement. That last part is the judgment automation could not handle, and it is what our explainer on workflow data means by records of how work actually gets done.

Quality checks done by hand during the workaround, if recorded, are related evidence; our page on quality assurance workflows covers that record type. If the company once wrote a design document for the automation, as described in our guide to the RPA process design document, it states the intended steps, which makes the gap between plan and reality visible.

Limits and unanswered questions

  • Run details can include personal data. Step inputs and outputs often carry names and addresses. Partners never ask for exports; rights and de-identification are handled in SourceX's review.
  • Volume is unknown until reviewed. Six weeks of rekeyed orders may be a few hundred records or many thousands. No one should estimate value from a conversation.
  • Fragile joins. If the manual tracker used customer names instead of order numbers, linking may not be possible.
  • Two separate payments. Any company compensation is agreed between the company and SourceX. Your reward is funded separately and never reduces it.

For examples of the wider record family, see the software workflow example pack, and for how agent connectors differ from classic automation tools, MCP vs Zapier. More guides are in the guides hub.

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 an operations leader mentions an automation that failed and a team that covered by hand, with order numbers on both sides, register, check the company on who qualifies, and read the terms before introducing the owner.

  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

Is an automation that was simply deleted still worth asking about?

Possibly. The run history may be gone, but the human side often survives: tickets, the manual tracker, and audit entries in the system people typed into. Those still show how the work was done by hand.

Who should I talk to about an old automation?

Start with whoever owns the process today, usually an operations or finance manager. The automation's builder may have left; the decision to discuss licensing sits with the CEO in any case, and in an owner-run company that is usually the owner.

Do failed runs contain customer data?

Often, yes, because run details can include the inputs and outputs of each step. That is one reason partners never ask for exports. SourceX handles rights review and de-identification under an agreement with the company.

Sources

  1. learn.microsoft.com/en-us/power-automate/fix-flow-failures
  2. learn.microsoft.com/en-us/power-automate/automation-center-overview
  3. help.zapier.com/hc/en-us/articles/20505304170637-Review-run-…
  4. help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs
  5. refer.sourcex.si/terms

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