Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Duplicate Order & Webhook Retry Audit

    1

    Trace duplicate orders and external effects through webhook, queue and retry failure windows. Get a scoped identity map, recovery plan and crash tests.

    $9

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Duplicate Order & Webhook Retry Audit

    Duplicate Order & Webhook Retry Audit

    Example session with this skill installed

    FICTIONAL supplied-evidence exercise; no live actions.

    Fictional audit only. Tenant A intent oi-4 event ev-7 reaches shipping worker. Worker calls provider without idempotency key then persists sent=true. Provider accepted first call but response lost; timeout occurs before local save. Queue retries; provider creates second shipment and distinct IDs are supplied. Owner suggests reuse same queue ID and wrap DB writes in transaction. Evaluate and give safe recovery/test plan; provider idempotency support unknown. No replay or cancellation.

    • Read your context and instructions
    • Compiled the duplicate order

    Duplicate/retry audit: retry-1

    Protected invariant: one intended shipment for tenant A business intent oi-4; retries may repeat transport attempts but must not silently create additional shipments or abandon unfinished work. This report uses fictional supplied evidence only. No replay, cancellation, provider lookup, network access or repair was performed. Provider identity, operation contract and idempotency retention/support remain unknown.

    Evidence: R1 = event ev-7/intent oi-4 reaches the shipping worker; R2 = worker calls provider without idempotency key, then writes sent=true; R3 = provider accepts first call but response is lost and worker times out before local save; R4 = queue retry creates second shipment and distinct provider IDs are supplied; R5 = owner proposes stable queue ID plus DB transaction.

    Timeline

    Exact timestamps were not supplied; relative ordering is supplied rather than invented clock times.

    Relative timeIdentityDurable local stateExternal evidenceGap
    t0A / ev-7 / oi-4Work reaches worker; ingestion/claim details unknownNone yetUpstream durability unknown
    t1Attempt 1 / oi-4sent flag not yet savedFirst shipment accepted, provider ID 1 suppliedRemote success precedes local result
    t2Attempt 1Timeout before sent saveAccepted effect persists; response lostOutcome uncertain to worker
    t3Queue retry / same intentLocal completion guard absentSecond shipment created, distinct provider ID 2 suppliedRetry repeats non-idempotent effect

    Key and transaction map

    LayerKnown identityRequired contract / unknown
    Eventtenant A, ev-7Provider/account scope and receipt dedup not supplied
    Business effectoi-4 shipment intentStable tenant/provider-account/operation/intent identity across retry and manual replay
    QueueRetry exists, ID unspecifiedQueue ID retention cannot define permanent business completion
    OutboundNo idempotency keyProvider support, key scope, payload binding and retention unknown
    Local resultsent=true after remote callDurable pending/claimed/uncertain/confirmed result states needed in existing effect owner

    Supported mechanism and counter-evidence

    R3/R4 support a confirmed duplicate in this fictional supplied trace, with high confidence: remote success → response loss → no local completion → repeated create. The distinct supplied provider IDs and same intent establish stronger correlation than repeated queue logs alone. No independent provider verification was performed. No evidence identifies an ingestion duplicate, queue bug, or payment/order duplicate.

    R5 does not close the failure window. A stable queue ID may reduce duplicate enqueue, but a retried worker still calls the provider; queue retention/removal also limits protection. A DB transaction can atomically record local state/outbox handoff but cannot roll back an accepted remote shipment. A local sent flag cannot prove remote failure when absent. Never retrying would also lose genuinely unfinished work.

    Narrow remedy and owner

    The shipping effect owner should reuse the existing intent/result ledger and retry ownership rather than introduce another queue. First establish provider support for this exact shipment operation and its scope/retention contract using separately supplied authoritative documentation. If supported, persist and reuse one tenant/provider-account/operation/intent-scoped idempotency key with canonical payload comparison and recorded provider result across attempts, DLQ and replay. An event-only key may be wrong if legitimate later events change the business action.

    If idempotency is absent or its window has expired, classify lost responses as uncertain. Block automatic repeat create until an authoritative lookup safely correlates the original effect, or an operator resolves the ambiguity. If lookup cannot distinguish outcomes, retain uncertainty; do not assume absence of a response means absence of a shipment. Use bounded attempts/duration, backoff and jitter, explicit retryable/terminal/uncertain states and one retry owner; provider-specific status classification is not supplied.

    Proposed acceptance and recovery

    Tests use fictional intent fixtures and a fake provider; none ran.

    Failure pointPersisted result expectedExact external-effect assertionTerminal outcome
    Normal shipmentConfirmed result with provider ID1 shipmentConfirmed
    Provider commits, loses response; idempotency supportedSame stable key/result reconciled1 shipment across retriesConfirmed after retry/lookup
    Same loss without idempotency/lookupDurable uncertain state1 initial effect; 0 additional create calls before resolutionUncertain, operator review
    Provider rejects before create, then safe retryBounded state/attempt history0 before success, 1 after successful permitted retryConfirmed or terminal per fake contract
    Worker dies after result commit before ackExisting confirmed result reused1 shipment totalConfirmed
    Concurrent claims or expired leaseOnly current owner may initiate effect; old worker cannot create anew1 with protected provider boundary, otherwise no additional uncertain createConfirmed or explicit uncertain
    Manual replay after queue removalBusiness result/key retained for replay policy0 additional shipment for completed intentConfirmed/deduplicated

    Operator recovery decision: preserve both supplied shipment IDs, correlation and state history; isolate this intent from automatic create retries. Obtain separately authorized authoritative status correlation, decide which existing shipment should fulfill the intent, and obtain explicit authorization before cancellation or another external action. Neither shipment was canceled or replayed here. Remaining unknowns are provider idempotency/lookup contracts, current shipment lifecycle and upstream receipt/claim durability; these preclude an exactly-once guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Trace receipt, durable acceptance, queue claim, business mutation, outbound effect and result persistence. Check tenant/provider-scoped identity, racing guards, premature processed markers, lease expiry, queue retention and uncertain remote success. Includes a failure-window worksheet, audit template and fictional worked example. Proposes bounded fake-provider tests and narrow remedies that reuse existing owners. It does not run a webhook server, replay production events, cancel shipments or promise exactly-once delivery across a remote API. Fictional supplied-evidence exercises are documented separately; no live provider, database, browser or cross-agent compatibility acceptance is claimed.

    Provider idempotency and lookup contracts must be verified; a timeout can leave an uncertain effect and cannot safely justify blind replay.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 21 days ago

    Permissions

    Read Files

    Read bundled and supplied redacted evidence only. Optional browsing, saving a report, implementation and external effects depend on host tools and task authorization. No provider account or credentials required for supplied-evidence review.

    Listed21 days ago

    What's inside

    Frequently Asked Questions

    Four Markdown files: SKILL.md, one method reference, one report template and a fictional worked example. The listing icon is a separate asset.

    No production connector, credentials or runtime are bundled. Supplied-evidence analysis works from authorized redacted material; live checks depend on separately authorized host tools.

    No. The default deliverable is an evidence-linked analysis and proposed next steps. Implementation, settings changes, messaging and deployment require the task authorization.

    Two fictional supplied-evidence forward exercises for this skill using Codex, plus frontmatter, linked-resource and ZIP round-trip checks. No live integration or other-agent compatibility validation is claimed.

    Provider idempotency and lookup contracts must be verified; a timeout can leave an uncertain effect and cannot safely justify blind replay.

    New in Testing & Debugging