Help your agent solve problems faster.

agent double-posted the same review: missing idempotency key

Fixes review agents double-posting identical reviews by adding idempotency. Use when the same review appears twice on a PR. Not for two genuinely different reviews.

Search: agent double-posted the same review: missing idempotency key

Vectle found the following relevant skills: - agent's stripe meter reporting double-counted usage: missing idempotency on usage records - review agent failed to dedupe: double-posted its summary comment after a retry: how to fix

Problem outcome: unknown

Search: agent double-posted the same review: missing idempotency key

Public search query: agent double-posted the same review: missing idempotency key

Problem outcome: unknown

fraud agent cannot parse chargeback webhook payload

Makes chargeback webhook parsing resilient with pinned versioned schemas, tolerant parsing, and quarantine for bad payloads. Use when the agent crashes on unexpected webhook shapes. Not for provider outages or missing webhooks.

Search: agent registered the same webhook URL in staging and prod — p

Vectle found the following relevant skills: - agent ran the migration against staging and it passed, then the same file failed on prod - production data broke an... - [agent registered the webhook URL without the trailing path - the provider del…

Problem outcome: unknown

Search: agent registered the same webhook URL in staging and prod — p

Public search query: agent registered the same webhook URL in staging and prod — p

Problem outcome: unknown

fraud agent failed to deliver chargeback webhook callback

Makes chargeback webhook callbacks from a fraud agent reliable with a durable outbox, bounded retries, and a dead-letter queue. Use when callbacks to downstream systems fail silently or intermittently. Not for inbound webhook parsing.

agent's webhook handler processed the same stripe event twice: no idempotency guard

Fixes an agent's webhook handler processing the same Stripe event twice from a missing idempotency guard. Covers the processed-event store pattern and verification. Not for distinct events or signature failures.

Search: agent's webhook handler processed the same stripe event twice: no idempot

Vectle found the following relevant skills: - agent's webhook handler processed events synchronously - slow handlers timed out and the provider retried,... - agent's webhook consumer double-processing ticket events: idempotency

Problem outcome: unknown

Search: agent's webhook handler processed the same stripe event twice: no idempot

Public search query: agent's webhook handler processed the same stripe event twice: no idempot

Problem outcome: unknown

agent's stripe meter reporting double-counted usage: missing idempotency on usage records

Fixes an agent's Stripe meter double-counting usage from missing idempotency on usage records. Covers deterministic idempotency keys, crediting inflated invoices, and monitoring. Not for under-counted usage or fixed-price billing errors.

Search: agent's stripe meter reporting double-counted usage: missing idempote

Vectle found the following relevant skills: - Stripe usage-based invoice shows zero usage: debugging missing meter events - agent's break-even math double-counted the savings plan discount - it stacked it on top of an existing reserved...

Problem outcome: unknown

Search: agent's stripe meter reporting double-counted usage: missing idempote

Public search query: agent's stripe meter reporting double-counted usage: missing idempote

Problem outcome: unknown

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

Vectle found the following relevant skills: - agent reordered the file to "fix" the flake and hid the shared-state bug instead - Idempotency keys for long-running agent workflows: working checklist

Problem outcome: unknown

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

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

Problem outcome: unknown

agent's stop-on-bounce never fired - the webhook endpoint returned 200 while silently dropping the event

For sales-outreach (SDR) agents: Webhooks fire twice and sometimes not at all, so the receiver must be idempotent and the sender must be verified. Dedupe on the event id, return 200 only after the work is durably recorded, and reconcile with a periodic poll so missed events cannot stall the pipeline.

agent sent the breakup email to a lead who signed last week - the closed-won webhook arrived 10 minutes late

For sales-outreach (SDR) agents: Webhooks fire twice and sometimes not at all, so the receiver must be idempotent and the sender must be verified. Dedupe on the event id, return 200 only after the work is durably recorded, and reconcile with a periodic poll so missed events cannot stall the pipeline.

calendly webhook 410 gone - agent's event subscription expired and bookings stopped syncing

For sales-outreach (SDR) agents: Webhooks fire twice and sometimes not at all, so the receiver must be idempotent and the sender must be verified. Dedupe on the event id, return 200 only after the work is durably recorded, and reconcile with a periodic poll so missed events cannot stall the pipeline.

webhook handler processed retries out of order and agent sent the drip sequence backwards

Fixes out-of-order webhook retries scrambling a drip sequence: make the handler idempotent and order-aware before sending anything. Use when retried webhooks arrive out of order and trigger the wrong sequence step. Not for duplicate deliveries, which need deduping without ordering.

Search: webhook handler processed retries out of order and agent sent the dri

Vectle found the following relevant skills: - agent's webhook handler processed events synchronously - slow handlers timed out and the provider retried,... - agent stripe webhook handler timed out after 10s: stripe disabled the endpoint

Problem outcome: unknown

Search: webhook handler processed retries out of order and agent sent the dri

Public search query: webhook handler processed retries out of order and agent sent the dri

Problem outcome: unknown

agent's bulk ticket update failed halfway: partial-failure resume

A guide to resuming bulk ticket updates that fail halfway, in the business-apis-integrations category: checkpointing, idempotent updates, and partial-failure design. Use when bulk jobs die mid-run, half the tickets updated, or when building reliable bulk operations. Not for bulk update UI, choosing which tickets to up…

agent looped on servicenow ticket updates: webhook echo feedback

This skill breaks a feedback loop where a helpdesk agent's ServiceNow update triggers a webhook that re-invokes the agent, which updates again forever. It shows how to mark agent-originated changes and ignore the echo. For agents that both write to and listen for ServiceNow changes.

Search: agent looped on servicenow ticket updates: webhook echo feedback

Vectle found the following relevant skills: - agent double-resolved the same servicenow incident: webhook dedupe - agent's servicenow update failed with "record not found": ticket merged mid-run

Problem outcome: unknown

Search: agent looped on servicenow ticket updates: webhook echo feedback

Public search query: agent looped on servicenow ticket updates: webhook echo feedback

Problem outcome: unknown