# Failed run to KB revision: the record chain | SourceX

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

A company connects failed-automation-to-policy-repair records through a chain of keys. The run ID joins the failed run to its alert ticket, usually automatically. Ticket numbers then have to be typed into macros, article version notes and later tickets by people, which is where the chain weakens. A single version note that cites the first ticket can hold the whole history together; without it, the article change looks unrelated to any failure. Partners can map which keys exist, and from which year, without opening a run, ticket or article.

This page is part of the [failed automation to policy repair guide](/guides/chain-failed-automation-to-policy-repair), which covers the packet of metadata to collect. Here the job is narrower: follow each key from one record to the next.

## The chain in one table: step, record, key and system

Each row is one record in the chain, the key it carries to the next record and whether software or a person writes that key.

| Step | Record | Key to the next record | System | Written by |
|---|---|---|---|---|
| 1. Run fails | Job or run with error and step | Run ID, workflow name, error text | Automation platform | Software |
| 2. Alert opens a ticket | Ticket with the failure | Run ID in subject or a field | Helpdesk | Software, if alerting is on |
| 3. Agent repairs by hand | Internal note on the ticket | Error code typed in the note | Helpdesk | Person |
| 4. Repeat failures | More tickets, same cause | Run IDs; seldom each other's ticket numbers | Helpdesk | Software for run ID, person for cross-links |
| 5. Workaround written | Macro or saved reply | Creation date only | Helpdesk | Person |
| 6. Instruction revised | Article version with note | Ticket number in the version note | Knowledge base | Person |
| 7. Configuration fixed | Mapping or workflow change | Change log entry, rarely a ticket number | Automation platform | Person |
| 8. Rule tested | Later ticket closed by following the article | Article ID or version cited on close | Helpdesk | Person |

Steps 1 and 2 are the strong end. Steps 5 through 8 depend on habits, and most companies have one or two of them, not all four.

## Following the BX12 failures through the keys (Illustrative)

A fictional 310-person industrial parts distributor syncs web orders into its ERP through an automation platform. Failures open helpdesk tickets for the order desk; instructions live in a help center. All values are invented.

- **Day 1, 07:40.** A run fails on an unknown unit-of-measure code, "BX12," on a new supplier's items. The alert opens a ticket with the run ID in the subject. Key held: run ID.
- **Day 1, 08:15.** An order desk agent re-keys 14 orders by hand, converting boxes to eaches, and names the code in an internal note. Key held: error code as text.
- **Days 3 to 30.** Seven more failures, seven more alert tickets, the same manual fix. Each ticket has its run ID; none cites the others. Key lost: the cross-reference that groups them.
- **Day 31.** A supervisor writes a macro with the conversion steps. Key lost: the macro records a creation date and nothing else.
- **Day 52.** The "ERP order sync exceptions" article gets a new section on supplier pack codes. Its version note cites the first ticket number. Key held, by one person's habit.
- **Day 60.** The mapping table is updated and BX12 runs succeed. Key lost: the change has no ticket reference.
- **Day 75.** A different code fails. The agent follows the revised article, closes in 10 minutes and cites the article version. Key held.

Remove the Day 52 version note and the chain splits into a run history, a pile of tickets and an article that seems to have changed for no reason. That one typed reference is the link the graphic highlights.

## Where the keys go missing

Six breaks account for most lost chains. Each is a fact the integration lead or support operations manager can confirm without looking at content.

1. **Hand-opened tickets.** Before alerting was switched on, or when an agent notices a problem first, the ticket has no run ID.
2. **Expired run detail.** Workato's documentation says job history retention depends on plan, and once it expires, job details including action inputs and outputs are deleted while job summaries remain. The run ID survives; what the run contained may not.
3. **Merged or closed-as-duplicate tickets.** Grouping repeat failures by merging can discard the separate run IDs.
4. **Unversioned edits.** An article edited in place, with no note, cannot be tied to any repair. Zendesk help center revisions show the differences between versions, but the reason for an edit is only there if someone wrote it.
5. **Revisions only some people can see.** Zendesk's documentation notes that light agents cannot see article revisions. The evidence may exist but be visible only to knowledge owners.
6. **Drafts that never publish.** In ServiceNow, an incident with the Knowledge check box selected creates a draft article on close, and the draft does not appear in the knowledge base until reviewed and published. The repair-to-instruction link can stop at an unreviewed draft.

For what happens to the reading of the case when only one system survives, see the sibling [before-and-after guide](/guides/failed-automation-to-policy-repair-missing-context). The [completeness checklist](/resources/failed-automation-to-policy-repair-completeness-checklist) scores each break.

## Questions that reveal which keys exist

Ask these at metadata level. Each answer marks one key as software-written, habit-written or absent, with a start year.

1. "Since when do automation failures open tickets on their own, and does the ticket carry the run ID?"
2. "How long is detailed run history kept on your plan, and have you ever exported it?"
3. "When the same failure repeats, how do agents group the tickets?"
4. "When an article changes, does the revision usually carry a note or a ticket number?"
5. "Who can see article revision history in your help center?"
6. "When a configuration change fixes a failure, is it logged against a ticket?"

For how integration failures are described as a data category, see [integration error handling records](/data-types/integration-error-handling-records); for written instructions, [internal knowledge bases](/data-types/internal-knowledge-bases). A company whose instructions live in process documents rather than a help center can still map the chain, as the [RPA process design document guide](/guides/rpa-process-design-document) and the page on [companies with no formal knowledge base](/questions/can-i-introduce-a-company-that-has-no-formal-knowledge-base) explain.

## Key holders and the CEO who can authorize

Each key has a keeper: the integration or IT lead for runs and configuration, the support operations manager for tickets and macros, the knowledge owner for article revisions. None of them alone can authorize licensing the joined history, because tickets and run payloads can hold customer, supplier and employee details. That decision sits with the CEO, often advised by the COO, CFO, CIO or general counsel.

Confirm the 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. Partners sign the Channel Partner Agreement before submitting introductions.

Unknown until SourceX reviews it: whether the company's rights cover each system's records, what must be removed, how complete each key is across years and what the company would be paid. SourceX does not claim a connector for every tool named here.

## 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 say which keys join its failed runs, repairs and article revisions, and from which year, [register as a partner](/register), check the company on [who qualifies](/who-qualifies) and read the [program terms](/terms) before you introduce the officer.

## 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
