Successful tasks are only half the story: agent recovery data in business workflows

Short answer

Agent recovery data is the record of a task that went wrong and was put right: the failed attempt, the signal that exposed it, the correction someone with authority approved, and evidence the fix held. Successful tasks show an AI agent the happy path; recovery records show it what to do after a wrong step. Field service callbacks, accounts payable holds, reopened support tickets and engineering rework often contain the full sequence.

Visual briefFull-size diagram
A service job path dips at a failed first visit, rises through a detected cause and an approved substitute part, and ends at a verified fix with no callback after 30 days.
Illustrative field service job. The three recovery segments are failure, authorized correction and verification.

What is agent recovery data, and which business records can illustrate it?

Recovery data is a trajectory with a dip in it. The work starts, a step fails, the failure is detected, a corrected plan is approved and carried out, and the result is checked. Each of those moments leaves a record in an ordinary business system if the company kept it.

Agent builders care about this because their systems fail in the middle of tasks, not only at the start. Appen, which sells agent training and evaluation data, offers trajectories with failure annotations and classifies where agents break down, such as misplanning or pursuing the wrong sub-goal, to decide what data to collect next. Research points the same way: the Reflexion paper showed that language agents improved when feedback from a failed attempt was turned into a written lesson and carried into the next attempt. A business record of a failed job, its diagnosis and its fix is a human-written version of that loop.

Records that commonly hold recovery sequences:

WorkflowFailure signalAuthorized correctionVerification
Field serviceFirst visit closed as incomplete; wrong part on vanSupervisor approves substitute part and revisitCompletion signature and no callback within a set window
Accounts payableInvoice placed on hold for price mismatchBuyer approves revised price or credit noteInvoice released and paid; vendor statement reconciles
Customer supportTicket reopened by the customer after closureEscalation lead approves a different fixTicket closed again and not reopened
Software engineeringDeployment rolled back after an alertReviewer approves a revised changeRedeploy passes checks and the alert stays clear
Order fulfillmentShipment refused or returnedCustomer service authorizes reship or refundDelivery confirmed or refund posted

The three segments of a recovery record

A useful recovery record has three segments, and each one answers a different question for the model developer.

  1. Initial failure. What was attempted, what state the work was in, and how the failure surfaced. The signal matters: a customer complaint, a failed check, a hold code.
  2. Authorized correction. Who diagnosed the cause, what alternative was chosen, and who approved it. Approval is the part most often missing, and it is what separates a real recovery from an improvised workaround.
  3. Verified recovery. Evidence that the corrected result held: a later check, a period with no repeat, a reconciled balance.

Missing any segment weakens the record. Failure without correction is an error log. Correction without verification is a hope. Verification without the failure is a success story with the useful part removed.

A worked example: one service job, failed and recovered

Illustrative. A fictional 240-person HVAC service company handles a commercial rooftop unit repair. All details are invented.

DayRecordSystemSegment
1Work order opened: unit not cooling; compressor fault suspectedField service managementStarting state
2Technician visit closed as incomplete: compressor on van does not fit this modelMobile work order notesInitial failure
2Return-to-stock entry for the wrong partInventoryInitial failure
3Service manager notes cause: model number mistyped at intakeWork order internal noteDiagnosis
3Substitute compressor approved under warranty; revisit scheduledApproval log and dispatch boardAuthorized correction
5Repair completed; customer signs offMobile work orderVerified recovery
35No callback logged for the unit in 30 daysField service managementVerified recovery

Seven entries across four systems tell a complete recovery story. The day 3 entries are the part a model cannot guess: that the root cause sat in intake, not in the repair, and that the substitute needed a named approver. The day 35 check is what lets an evaluator call the recovery verified rather than claimed. The field service histories page covers the systems involved, and root cause analysis records cover the diagnosis step in more formal settings.

How is this different from failure data, exceptions and corrections?

The guide to why AI labs value records of mistakes and rework explains why failed attempts are worth keeping at all. Recovery data, as this page uses the term, adds two tests: a named approval for the fix, and a later check showing the fix held. Exception handling records explain how a case outside the normal rules was decided; the exception handling guide covers them. Correction workflows, covered in assessing human review records, focus on a reviewer fixing someone else's output. Recovery data is narrower and sequential: the same task, attempted, failed, re-planned and confirmed. One recovery record can contain an exception and a correction, but the test is whether the whole arc is linked to one job, ticket or invoice. The agent trajectory data explainer defines trajectories more generally.

Company qualification questions

Keep discovery at metadata level. The partner learns whether the arc exists, not what any job said.

AskStrong answerWhy it matters
When a job, ticket or invoice fails, is the rework linked to the original record?Same ID, or a parent-child linkWithout the link the arc cannot be rebuilt
Does the system record who approved the fix?Named approver with timestampSeparates authorized corrections from workarounds
Is there a later check, such as a callback window or reopen flag?Yes, reported monthlySupplies the verification segment
How many years of history are kept, and in which systems?Five or more years in named toolsDepth and continuity
Who can authorize a licensing discussion?The CEO, usually the owner in an owner-run companyThe right sponsor

The introduced company needs 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.

Special situations can matter here. Investors and advisors handling a wind-down often hold years of rework history in systems about to be switched off; the special situations investor page covers that case.

What stays unknown until SourceX reviews it: current buyer interest in this record type, the rights review result, redaction treatment of customer and technician names, and any offer to the company.

Limits and unanswered questions

SourceX has not published figures on how often recovery records are requested or what they are worth, and this page makes no such claim. The research cited shows that feedback from failures can improve agents; it does not show that any particular archive will be licensed. Failure records can also be sensitive. Callback notes may describe safety issues or customer disputes, and the company decides scope before anything is reviewed.

Company compensation and referral rewards are separate. The company is paid under its own agreement with SourceX; the partner's reward is calculated on what SourceX actually pays the company and is funded separately, so it never reduces the company's payment. Illustrative only: on a $120,000 payout, the reward would be $56,000. See how rewards work.

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 a client links rework to the original job and records who approved the fix, register as a partner, check the company against who qualifies and read the program terms before introducing its decision-maker. More agent data topics are in the guides hub.

  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 recovery data just another name for error logs?

No. An error log records that something failed. Recovery data also records how the failure was noticed, who approved the fix and evidence that the fix held. Without the last two parts, it is only half a story.

Do companies need to have used AI agents to hold recovery data?

No. The records described here come from people doing the work. AI developers can study how people recovered from failures whether or not any agent was involved at the time.

Can I describe a client's failed jobs to SourceX?

Only at metadata level and with the owner's agreement: which system, how many years, whether rework and approvals are linked. Never share customer details, job files or screenshots.

Sources

  1. appen.com/agentic-ai
  2. appen.com/agentic-ai-trajectory-analysis
  3. arxiv.org/abs/2303.11366
  4. 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