# Automation run log missing context: before/after | SourceX

Canonical: https://refer.sourcex.si/guides/failed-automation-to-policy-repair-missing-context
Last updated: 2026-11-04

A single-system export of a failed automation keeps what failed, when and with which error. It loses what people did about it: the invoices a clerk matched by hand, the judgment behind the fix, the macro and article that turned the fix into a rule, and the later tickets showing the rule worked. Read alone, a failure the business absorbed by hand for weeks looks like a short glitch that fixed itself. The missing context lives in the helpdesk and the knowledge base.

This page is part of the [failed automation to policy repair guide](/guides/chain-failed-automation-to-policy-repair). It reads one fictional case twice: from the automation platform's run history alone, then with the tickets and article revisions around it.

## Before: the invoice-routing failures as the run log tells them

Illustrative. A fictional 520-person building-materials wholesaler routes supplier invoices from an accounts payable inbox to approvers through an automation platform. A reviewer sees only the run history export. Every value is invented.

| Field in the run history | Value |
|---|---|
| Workflow | Supplier invoice capture and approval routing |
| Failed runs | 11 over three weeks |
| Error | "PO number not found" at the extraction step |
| Affected sender | One supplier's billing address |
| Week 6 onward | Invoices from that supplier route normally |
| Inputs and outputs | Available only within the plan's retention window |
| Who did what | Not recorded |

### What a reader concludes

One supplier's invoices failed to parse for three weeks, then the template was fixed. Eleven failures look like eleven invoices delayed, perhaps paid late. Nothing says a clerk matched each invoice to a purchase order by hand, that two clerks applied different standards, or that anyone wrote down how to treat invoices without a readable PO.

The export may be thinner still. Workato's documentation says job history retention depends on plan, 30 days on some and configurable up to 90 days on others, and that once it expires, job details including action inputs and outputs are deleted while summaries remain. A reviewer a year later may see only that eleven runs failed.

## After: the same failures with tickets and article revisions

Restore the AP service desk and the finance knowledge base, and the three weeks become a story about people.

- **Service desk, week 1.** The first alert ticket shows an AP clerk finding the PO number printed in the remittance footer after the supplier redesigned its invoice, then keying the match by hand.
- **Service desk, weeks 1 to 3.** Ten more tickets. Two clerks apply the same fix; one also confirms the receiving record before approving, the other does not.
- **Service desk, week 3.** The AP lead saves a reply template: find the footer PO, check receipt, route to the buyer.
- **Knowledge base, week 5.** The "Invoices without a readable PO" article is revised to require the receipt check. The version note cites the first ticket.
- **Automation platform, week 6.** The extraction template is updated for the new layout. Only now do runs succeed.
- **Service desk, week 9.** A different supplier's invoice fails the same way; a clerk follows the revised article, including the receipt check, and closes the same morning.

The reader now sees three weeks of manual matching, two clerks applying different standards, a written rule that settled which standard was right, a template fix that came last, and evidence that the rule worked on a new supplier. Zendesk help center revisions show the differences between versions, so the article change itself is inspectable; the reason for it is visible only through the ticket number in the note.

## The lost-context table: what a run export drops and where it lives

Each row is context the automation platform cannot hold, the system that usually holds it and the person who can say whether it exists.

| Context | Run export alone | Where it lives | Who can confirm it exists |
|---|---|---|---|
| Business impact | Not included | Ticket notes: invoices, discounts or accounts touched | Support operations manager |
| The manual fix and its reasoning | Not included | Internal ticket notes | Support operations manager |
| Who approved the workaround | Not included | Ticket assignee, supervisor note or macro owner | Support operations manager |
| Grouping of repeat failures | Separate failed runs | Ticket tags, linked tickets or problem records | Support operations manager |
| The written rule | Not included | Macro, article revision or SOP | Knowledge owner |
| When the rule changed, and why | Not included | Article revision history and version note | Knowledge owner |
| Proof the rule worked | Not included | Later tickets citing the article | Support operations manager |
| Run inputs after retention expires | Summary only | Exported run history, if anyone kept it | Integration or IT lead |
| Repairs that never became a rule | Invisible | Recurring fixes with no matching article | Support operations manager |

The last row matters most. A workaround applied again and again in the helpdesk but never written into the documented process is the case where the run log and the knowledge base both look complete and the company's real rule exists only in agents' habits. Tools can create the gap without anyone being careless: in ServiceNow, an incident with the Knowledge check box selected creates a draft article on close, and the draft stays out of the knowledge base until it is reviewed and published. For how the keys rejoin the columns, see the sibling guide on [failed automation to policy repair record linkage](/guides/failed-automation-to-policy-repair-record-linkage).

## Why the right-hand column is the useful part

For AI training and evaluation, the run log alone teaches a model that systems fail. The connected history shows an exception, a human decision, a written rule and a test of that rule, which is the sequence agents most need and most often lack, as [why AI agents fail](/questions/why-ai-agents-fail) discusses. The [journal entry automation example](/resources/mcp/mcp-journal-entry-automation) shows the same exception-to-rule pattern in a finance workflow. For the categories themselves, see [integration error handling records](/data-types/integration-error-handling-records) and [internal knowledge bases](/data-types/internal-knowledge-bases).

## Scoping what the company can restore

A partner learns which rows of the table the company can restore, from which year and who controls each system. You ask; you do not collect.

- **Records that exist:** run history and any exports, failure tickets, macros, article revisions or SOP versions, configuration change logs.
- **Who owns them:** the integration or IT lead, the support operations manager and the knowledge owner.
- **Who can authorize a licensing discussion:** the CEO, often advised by the COO, CFO, CIO or general counsel, because tickets and payloads can hold customer and supplier details.
- **Company baseline:** 50+ full-time employees at peak (contractors excluded), 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.
- **Unknown until SourceX reviews it:** whether rights cover each system, what must be removed, which years a buyer wants and what the company would be paid.

If a client tried to sell data before and it stalled, [why past data monetization failed](/questions/data-monetization-failed) covers what carries over. The [completeness checklist](/resources/failed-automation-to-policy-repair-completeness-checklist) turns the table into scored questions.

## 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 your client can restore the tickets and article history behind its failed runs, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the CEO, who can authorize it.

## Sources

- https://refer.sourcex.si/terms
- https://docs.workato.com/security/data-protection/data-retention/
- https://support.zendesk.com/hc/en-us/articles/4408829321498-Viewing-article-revisions-and-restoring-a-previous-version
- https://docs.servicenow.com/bundle/orlando-it-service-management/page/product/incident-management/task/create-knowledge-incident.html
