# Change collision recovery: a worked case | SourceX

Canonical: https://refer.sourcex.si/guides/change-collision-recovery-exception-examples
Last updated: 2026-11-04

The records that explain this kind of failure are the ones that show two changes passing review separately, the failure they caused together, the decision about which one to roll back, and the fix to the process afterward: both change requests and their approvals, the conflict check result, the monitoring alert, the incident with its correlated recent changes, the emergency rollback approval, the restore time and the post-incident review. Each change record looks clean alone. The value is in the set.

This worked case belongs to the [change collision recovery guide](/guides/workflow-change-collision-recovery), which covers what a platform merger can leave behind. Here the job is narrower: follow one bad night from the first approval to the final fix, mark who decided each step and which record proves it, then turn that into signs an ITSM implementation partner can recognize at a client.

## The case: a database patch and a load balancer change on the same night

Illustrative. A fictional 650-person software and hosting company runs its change process in one tool and its on-call response in a separate incident platform. On one Saturday night two changes were scheduled.

- **Change A** patched a database cluster. A normal change, approved at the weekly change advisory board, planned 01:00 to 03:00.
- **Change B** updated a load balancer configuration. A pre-approved standard change, planned from 01:20 the same night.

Each change was correct for the component it touched. The checkout service, however, relied on both the database cluster and the load balancer, and nobody had written that link into the inventory of components. That is the exception: two individually approved changes that conflict.

## The night, step by step

| Step | Time | What happened | Who decided | Record that proves it |
|---|---|---|---|---|
| 1 | Wednesday | Change A approved for Saturday 01:00 to 03:00 | Change advisory board | Change request, approval, CAB notes |
| 2 | Pre-approved | Change B scheduled from 01:20 | Standard change template owner | Change request on a standard template |
| 3 | Before the window | Conflict check on both: no conflicts listed | The ITSM tool | Stored conflict result |
| 4 | 01:40 | Checkout error rate crosses its alert threshold | Monitoring rules | Alert with timestamp |
| 5 | 01:45 | Incident opened; change B shown as a recent change, correlated by time | On-call engineer | Incident with recent-change correlation |
| 6 | 02:05 | Roll back change B; let change A finish | Change manager | Emergency rollback approval with reason |
| 7 | 02:20 | Alert clears; incident resolved | On-call engineer | Incident resolution time |
| 8 | Following week | Review finds the missing link and records it | Problem manager | Post-incident review; inventory relationship change |

## Reading each record: what it proves

The table lists the records. The point of a worked case is what each one shows that the others cannot.

- **Step 3, the empty conflict result.** ServiceNow's conflict detection works from the change's configuration item and planned dates, and reports issues such as CI already scheduled, not in maintenance window, or blackout. Changes A and B sat on different CIs, so the check had nothing to flag. A stored "no conflicts" result proves the check ran and records the limit of what it could see.
- **Step 5, the correlation.** In PagerDuty, an incident's Recent Changes section shows up to three changes correlated from the past 24 hours, with a reason such as time or related service. Related-service matches depend on configured service dependencies; here only time linked them. The record shows how the suspect was found, and why a better dependency map would have found it faster.
- **Step 5 also depends on step 2 being visible.** Change events do not page anyone; they appear only as context. PagerDuty's ServiceNow integration can create those change events when a change request is opened. If the integration was off, step 5 would show nothing.
- **Step 6, the choice under pressure.** Rolling back the database patch mid-window would have been riskier than undoing a configuration change. The change manager's approval note, with its reason, records a judgment no rule makes.
- **Step 8, the correction.** The CMDB relationship added after the review is what stops the next collision. Its date matters: a dependency added after the incident should not be read as one that existed before.

## Why this sequence is useful evidence

Records 3, 6 and 8 carry the judgment: what the review process could not see, which change to sacrifice, and what was changed so it would not recur. Public documentation describes how conflict detection and correlation work. It cannot show an experienced team deciding, at 02:05, which of two approved changes to undo.

For AI developers building IT operations agents, that ordered chain of decision, outcome and correction is the scarce part, as [why AI agents need work data](/proof/ai-agents-need-work-data) explains. Agents tend to fail exactly where the documented process runs out, a theme covered in [why AI agents fail](/questions/why-ai-agents-fail). The same problem, action and outcome shape appears in freight in [logistics exceptions and their documented resolutions](/guides/how-to-identify-logistics-exceptions-and-their-documented-resolutions).

## Spotting similar cases at a client

An ITSM implementation partner can usually tell in one conversation with the service delivery director whether a client has cases like this.

1. **Post-incident reviews cite change numbers.** If reviews name the changes involved, collisions can be found later.
2. **Conflict results are stored, not just displayed.** Ask whether conflict checks are saved on the change record.
3. **Change events reach the on-call tool.** An ITSM-to-on-call integration means recent-change correlations exist on past incidents.
4. **Emergency rollbacks get their own approval.** A separate emergency change or back-out task with an approver makes step 6 attributable.
5. **CMDB relationship history is kept.** Without it, nobody can tell whether a dependency existed on the night.
6. **There is a real date ahead.** An ITSM consolidation, an on-call tool switch or a managed services handover puts the history at risk.

Note metadata only: tools, years, rough counts of change-related major incidents, owners. Do not export incidents, take screenshots or pull samples. The [records across systems map](/guides/change-collision-recovery-records-across-systems) shows how these records join, and the [who can license answer](/questions/who-can-license-change-collision-recovery-records) covers whom to introduce. For ticket-level context, see [ServiceNow incident data](/systems/servicenow-incident-data-for-ai-training).

## Qualification and what stays open

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

What stays unknown until SourceX reviews it: buyer interest in collision history, how client contracts affect records about services run for customers, which years are selected, and whether an offer follows.

## 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's reviews can still trace a collision from the conflict check to the CMDB fix, [register as a partner](/register), check the company on [who qualifies](/who-qualifies), and read the [program terms](/terms) before you introduce the service delivery director.

## Sources

- https://docs.servicenow.com/bundle/paris-it-service-management/page/product/change-management/task/t_RunManualConflictDetection.html
- https://support.pagerduty.com/docs/change-events
- https://support.pagerduty.com/main/docs/servicenow-change-requests-integration-guide
- https://refer.sourcex.si/terms
