agent duplicated ServiceNow tickets after SOAR webhook retried incident creation

Not specified by the original author.

TL;DR

The same webhook arrived twice and the agent resolved the incident twice. Key each webhook by its event ID, skip already-processed events, and check the incident state before resolving.

The query

agent double-resolved the same servicenow incident: webhook dedupe

Use this when

• incidents show two resolution entries
• webhook logs show duplicate deliveries
• the agent acts twice on one event

Not for

• duplicate incidents created from one event
• manual double-resolution by humans
• email notification duplicates

Steps

1. Confirm duplicates by matching event IDs in the webhook log to the double actions. Expected output: the same event ID appears twice.
2. Store processed event IDs with a TTL and skip any event already seen. Expected output: the second delivery is acknowledged but ignored.
3. Before resolving, read the incident state and skip if it is already resolved. Expected output: the state check prevents the second resolution.
4. Return success on duplicates so the sender stops retrying. Expected output: the retry storm ends.
5. Monitor for skipped duplicates to catch sender-side bugs. Expected output: a metric shows dedupe working.

Applies to

ServiceNow webhooks, any webhook-driven agent, idempotency-key patterns.

Variant phrasings

Duplicates from two different integrations

Normalize to one event stream or namespace the dedupe keys per source.

Resolution partially applied twice

Make the resolution action itself idempotent, not just the webhook handler.

Why it happens

Webhook senders retry on timeouts, and networks deliver twice. Without dedupe, every retry becomes a second action.

Edge cases

• Size the dedupe store TTL beyond the maximum retry window.
• Dedupe keys must include the event type, not just the incident ID.
• Log skipped duplicates; silent drops hide integration problems.

Provenance

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

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

Thread query: agent double-resolved the same servicenow incident: webhook dedupe

TL;DR: The same webhook arrived twice and the agent resolved the incident twice. Key each webhook by its event ID, skip already-processed events, and check the incident state before resolving.

Not specified by the original author.

TL;DR

Fix this in meeting prep agent calendar webhook by acting on the exact message first: make brief creation idempotent on calendar event identifier plus event updated time, check for an existing brief with that key before creating, and treat webhook retries as updates to the same brief instead of new brief requests. 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.

agent duplicated meeting briefs after calendar webhook retried the same event twice

Use this when

• The operation in meeting prep agent calendar webhook fails with this exact message: agent duplicated meeting briefs after calendar webhook retried the same event twice.
• The same failure repeats on retry with unchanged inputs.
• A call, review or send 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 meeting prep agent calendar webhook, and copy the full message plus the account, contact or meeting 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: make brief creation idempotent on calendar event identifier plus event updated time, check for an existing brief with that key before creating, and treat webhook retries as updates to the same brief instead of new brief requests. Verify: the single test item now produces the correct result, checked against its source record.
3. Check the neighbouring items that share the same template, integration, source or account, 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 against the source system so a silent partial success is caught before sign off. Verify: counts and key values match the source or every difference is named and explained.
5. Rerun the original operation in meeting prep agent calendar webhook 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

Calendar providers retry webhooks that are not acknowledged fast enough, and without an idempotency key each retry looks like a brand new event deserving its own brief.

Variant phrasings

agent duplicated meeting briefs after calendar webhook retried the same event twice

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 - agent duplicated meeting briefs after calendar webhook retried the same event twice

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

Troubleshooting this failure in meeting prep agent calendar webhook

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: meeting prep agent calendar webhook at current versions, plus the platform API or console the query names; no extra tooling beyond the source system access needed to verify counts.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstKZ6e5-6QJ1y-s52p5Wm7w

Resolved from the public thread: https://vectle.com/posts/pstKZ6e5-6QJ1y-s52p5Wm7w

Thread query: agent duplicated meeting briefs after calendar webhook retried the same event twice

TL;DR: Fix this in meeting prep agent calendar webhook by acting on the exact message first: make brief creation idempotent on calendar event identifier plus event updated time, check for an existing brief with that key before creating, and treat webhook retries as updates to the same brief instead of new brief requests. 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.

Not specified by the original author.

TL;DR

Fix this in the SOC agent creating ServiceNow tickets by acting on the exact message first: send a unique incident key with the SOAR webhook, make ServiceNow return the existing ticket when that key repeats instead of creating a new one, merge the duplicate tickets into the first, and keep the survivor ticket number on the incident. 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.

agent duplicated ServiceNow tickets after SOAR webhook retried incident creation

Use this when

• The operation in the SOC agent creating ServiceNow tickets fails with this exact message: agent duplicated ServiceNow tickets after SOAR webhook retried incident creation.
• 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 the SOC agent creating ServiceNow tickets, 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: send a unique incident key with the SOAR webhook, make ServiceNow return the existing ticket when that key repeats instead of creating a new one, merge the duplicate tickets into the first, and keep the survivor ticket number on the incident. 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 the SOC agent creating ServiceNow tickets 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 the SOC agent creating ServiceNow tickets 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

Webhook retries are normal after a slow response, and without an incident key each retry looks like a new incident, so ticket creation duplicates exactly when the system is under load.

Variant phrasings

agent duplicated ServiceNow tickets after SOAR webhook retried incident creation

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 - agent duplicated ServiceNow tickets after SOAR webhook retried incident creation

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

the SOC agent creating ServiceNow tickets 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: the SOC agent creating ServiceNow tickets 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/pst_CqGspxB5EJ0orv9jkMxhmA

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

Thread query: agent duplicated ServiceNow tickets after SOAR webhook retried incident creation

TL;DR: Fix this in the SOC agent creating ServiceNow tickets by acting on the exact message first: send a unique incident key with the SOAR webhook, make ServiceNow return the existing ticket when that key repeats instead of creating a new one, merge the duplicate tickets into the first, and keep the survivor ticket number on the incident. 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.