PagerDuty error "incident already exists" duplicate alert suppressed real escalation

Not specified by the original author.

TL;DR

Fix this in PagerDuty by acting on the exact message first: narrow the PagerDuty deduplication key so it includes the affected service and alert fingerprint instead of only the integration name, close the wrongly suppressed duplicate record, and create a fresh incident for the real escalation so on call is paged. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.

PagerDuty error "incident already exists" duplicate alert suppressed real escalation

Use this when

• The operation in PagerDuty fails with this exact message: PagerDuty error "incident already exists" duplicate alert suppressed real escalation.
• The same failure repeats on retry with unchanged inputs.
• An alert, incident or enrichment step is blocked until this item completes.

Not for this skill when

• The message is a permission or outage notice from the platform. Resolve that first, then return here if this error remains.
• The operation completes and you only disagree with its output. That is a quality review, not this failure.

Steps

1. Reproduce the failure with the smallest scope that still shows it in PagerDuty, and copy the full message plus the alert, incident or enrichment record involved into the run notes. Verify: the error is reproduced on demand with a named item, not only seen in a log.
2. Apply the specific fix for this error: narrow the PagerDuty deduplication key so it includes the affected service and alert fingerprint instead of only the integration name, close the wrongly suppressed duplicate record, and create a fresh incident for the real escalation so on call is paged. Verify: the single failing item now behaves as the fix predicts, or the corrected value is visible on the record.
3. Check the neighbouring items that share the same config, template, feed or credential, because this class of failure rarely affects only one item. Verify: the neighbouring items are listed and each is marked affected or clear.
4. Compare the result counts, decisions or alerts against the source in PagerDuty so a silent partial success is caught before sign off. Verify: counts match the source or every difference is named and explained.
5. Rerun the original operation in PagerDuty on the previously failing scope, watching for the same message rather than assuming success from a quiet log. Verify: the operation completes and the original message does not appear.
6. Record the fix, the triggering input and the verification result on the item so the next occurrence is recognised immediately. Verify: the record names the error, the fix applied and the evidence of success.

Why it happens

PagerDuty suppresses a new incident when its deduplication key matches an open one, and a key built too broadly makes a genuinely different escalation look like a repeat of an earlier alert.

Variant phrasings

PagerDuty error "incident already exists" duplicate alert suppressed real escalation

The verbatim form searchers paste from the terminal or console. Treat it identically: same fix, same single item proof, then the full rerun.

How to fix - PagerDuty error "incident already exists" duplicate alert suppressed real escalation

The how-to phrasing for the same failure in PagerDuty. The steps above apply unchanged; start at the reproduction step rather than skipping to the rerun.

PagerDuty troubleshooting for this failure

The symptom-first phrasing used when the console hides the full message. Surface the full message first, confirm it matches the code block above, then follow the steps.

Compatibility: PagerDuty at current versions, plus the platform API or console the query names; no extra tooling beyond a text editor and the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/psttIdsZDw9TJs9tsZcd64uQ

Resolved from the public thread: https://vectle.com/posts/psttIdsZDw9TJs9tsZcd64uQ

Thread query: PagerDuty error "incident already exists" duplicate alert suppressed real escalation

TL;DR: Fix this in PagerDuty by acting on the exact message first: narrow the PagerDuty deduplication key so it includes the affected service and alert fingerprint instead of only the integration name, close the wrongly suppressed duplicate record, and create a fresh incident for the real escalation so on call is paged. Do not rerun the whole job unchanged, because the same inputs produce the same failure. Prove the fix on one item, then rerun the full scope and reconcile the counts.