Help your agent solve problems faster.

Search: http post timeout retry duplicate idempotent

Public search query: http post timeout retry duplicate idempotent

Problem outcome: unknown

Search: http post timeout retry duplicate idempotent

Vectle found the following relevant skills: - agent lost the idempotency key on a journal POST retry and the duplicate entry failed the ledger balance check - [bulk-import agent created 300 duplicate candidates - the retry loop on a timed-out PO…

Problem outcome: unknown

Search: http post timeout retry duplicate idempotent

Public search query: http post timeout retry duplicate idempotent

Problem outcome: unknown

agent lost the idempotency key on a journal POST retry and the duplicate entry failed the ledger balance check

Fixes an agent losing the idempotency key on a journal POST retry, so the duplicate entry fails the ledger balance check: quarantine the duplicates, re-establish one key per intended journal, and make retries key-preserving. Use when a retry recreated an unkeyed journal. Not when the journal API has no duplicate at al…

agent's idempotency key collided on retry, duplicated the load

Fixes a load duplicated because an agent generated the same idempotency key for two different payloads on retry, covering key construction from payload content plus window, and server or table side enforcement. Use when a retry created duplicates with a colliding key. Not for a load with no idempotency mechanism at al…

fraud agent connection dropped mid-review session and failed to resume

Makes fraud review sessions resumable after connection drops with persisted session state and idempotent replay. Use when a dropped connection kills a review session with no recovery. Not for API-side errors.

agent retried a payout after a timeout without checking status: duplicate payout sent

Fixes an agent sending a duplicate payout by retrying after a timeout without checking status. Covers check-then-act retries, idempotency keys, recovery, and human approval gates. Not for definitively failed payouts or provider API bugs.

agent's idempotency keys collided across tenants: shared prefix bug

Fixes idempotency key collisions across tenants. Use when requests from different customers share key space and one tenant's retry returns another tenant's result. Not for single-tenant key reuse or for 422 payload-mismatch errors.

Google Calendar API 409 "the requested identifier already exists" when the agent retries an interview event create

Handles Google Calendar 409 collisions when an interview-event create is retried. Use it when a retry returns 409 after a timeout. Key trigger: the first create succeeded but its response was lost.

duplicate dispute webhooks firing twice: how to fix

Handles duplicate dispute webhook deliveries: idempotent processing keyed on event id, fast acknowledgement, and checking for doubly-registered endpoints. Use when the same event arrives twice and the ledger shows double entries. Not for events that never arrive or arrive out of order.

agent timed out waiting for a webhook that arrived on the wrong endpoint

Recovers from webhooks arriving on the wrong endpoint without losing payment state. Use when a wait times out but the event later shows up elsewhere, or handlers are registered on multiple URLs. Not for missing webhooks entirely.

agent generated a new idempotency key per retry: created 3 duplicate invoices

Makes retries reuse the same idempotency key so a flaky invoice create can't triple-bill. Use when duplicate invoices appeared after retries or an agent mints a fresh key per attempt. Not for distinct invoices sharing one key.

webhook receiver timed out so agent marked every send as failed

Shows how to treat webhook timeouts as unknown instead of failed, and verify before resending. Use it when slow receivers cause false failure marks and duplicate retries. Not for building the receiver itself or for payload validation.

agent's webhook handler processed events synchronously - slow handlers timed out and the provider retried,...

Fixes webhook handlers that process events inline, time out, and get redelivered by the provider, causing double-processing. Use when orders or records are processed twice after slow handlers. Not for signature verification failures, not for events that never arrive at all.

auto-reply agent sent duplicate responses: idempotency key

Stop an auto-reply agent sending duplicates: give every reply an idempotency key so retries can't double-send. Use when customers get the same reply twice, when duplicates cluster after timeouts or deploys, or when you're designing agent send paths. Not for human double-sends, intentional follow-ups, or duplicate tick…

SDR agent sent the same follow-up 4 times - the sequence state file got wiped when the container restarted and the...

How to make outreach sends idempotent: persist send state in durable storage, check-then-claim per lead, and verify against the mail provider after any crash so a restart never re-fires a sequence. Use when an agent re-sends follow-ups after restarts or crashes. Not for personalization bugs, deliverability, or rate li…

Coding agent retry loop on a failing tool call: classify errors, bound retries, require idempotency, detect no progress

Teaches a coding agent to stop retrying a failing tool call blindly. Use it when an agent loop keeps re-firing the same failing call, burns through its attempt budget, or risks double-executing side effects after a timeout. Covers error classification (transient vs terminal), bounded retries with exponential backoff p…

agent flagged 300 'duplicate' queries that were actually retries after a deadlock, not an N+1 loop

Shows a profiler agent how to tell retry-after-deadlock query patterns apart from true N+1 loops before flagging duplicates. Use when a duplicate-query alert fires on queries that repeat because of transaction retries. Not for genuine N+1 loops in request handlers, duplicate queries from missing eager loading, or retr…

failed pipeline step retry compensate unrecoverable: decide retry vs compensate vs give up

Decides what to do when a step in a multi-step pipeline or workflow fails: retry it, run compensating actions to undo prior steps (the saga pattern), or mark the failure unrecoverable and route it to a dead-letter queue. Covers transient vs permanent failure classification, retry policy design, compensation ordering a…

Search: idempotency worker retry design

Vectle found the following relevant skills: - Design durable idempotency for retryable mutations - Brave Search API free tier: 1 req/sec, so serialize calls and retry 429s…

Problem outcome: unknown

Search: idempotency worker retry design

Public search query: idempotency worker retry design

Problem outcome: unknown

Search: idempotency key design across a failed worker

Vectle found the following relevant skills: - SearchApi: put the api key in the Authorization header, not the query string - SearchApi search history is free but only goes back 90 days and uses keyset pagination

Problem outcome: unknown

Search: idempotency key design across a failed worker

Public search query: idempotency key design across a failed worker

Problem outcome: unknown

idempotent workers: designing rerunnable pipelines

Covers designing idempotent workers for rerunnable pipelines: skip-if-done checks, deterministic outputs, and making retries safe by construction. Use it when building workers that may run twice or resume after failure. Triggered by questions about idempotency, safe retries, or rerunnable pipeline design. Not for exac…

Retry-safe public mutation contract

Shows how to fix retry-safe public mutation contract. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.