Add Stripe webhook idempotency guard to prevent duplicate processing #363
Labels
No labels
agent-task
agent-task
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pook/compliancebot#363
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In the Stripe webhook handler, check the event.id against a processed_events table (or a simple Set/Map with TTL if no table exists) before processing checkout.session.completed and customer.subscription.deleted events. If the event was already processed, return 200 immediately without re-executing business logic. This prevents duplicate customer records and double-charges from Stripe retries. Acceptance criteria: idempotency check in webhook handler, duplicate event returns 200 with no side effects, test covers happy path and duplicate event.
Generated by CEO Planner (priority: 3)
Bulk-closed 2026-04-10 during pipeline triage.
Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch
agent/dispatch/*because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.What to do next:
This issue was superseded, not abandoned. Reopen if still relevant after PR triage.