Blockforge — Production-grade shadcn blocks, forged to ship

You10:42

Retries from our billing provider are creating duplicate invoices. Can you review app/api/webhooks/route.ts and make the handler idempotent? We use Drizzle and Postgres 16.

route.tsTypeScript · 4.2 kBwebhook-retry.logLog · 18 lines

AnvilAnvil Sonnet10:42Streaming

Read 3 files and replayed the retry14s

Read route.ts, schema.ts and the last 4 deliveries in webhook-retry.log.
Reproduced the race with two concurrent invoice.paid requests.
Checked the migration history for an existing unique key.

Found it. The handler does a read-then-insert: it looks for an existing invoice, then writes one if none exists. The provider can deliver the same invoice.paid event twice before either request commits, so both pass the read and you get two rows.

Smallest safe fix. Add a unique key on the provider event and turn the invoice write into an on conflict do nothing insert. No backfill needed.

Record every provider event in a new billing_events table before touching invoices.
Make invoice.paid a no-op when the event was already handled.
Return 200 on duplicate delivery so the provider stops retrying.

Here's the handler after the change:

TypeScript

import { headers } from "next/headers";

import { db } from "@/lib/db";

import { billingEvents, invoices } from "@/lib/schema";

import { verifySignature } from "@/lib/billing";

export async function POST(request: Request) {

const signature = (await headers()).get("stripe-signature");

const event = verifySignature(await request.text(), signature);

const [seen] = await db

.insert(billingEvents)

.values({ provider: "stripe", eventId: event.id, type: event.type })

.onConflictDoNothing()

.returning({ id: billingEvents.id });

if (!seen) return Response.json({ duplicate: true });

if (event.type === "invoice.paid") {

await db.insert(invoices).values(toInvoice(event)).onConflictDoNothing();

}

return Response.json({ received: true });

}

Ship the migration first, then the handler. The duplicate path is safe to deploy without a backfill, and the new log line will tell you when a retry was collapsed.

Sourcesroute.ts4.2 kBschema.ts2.8 kBwebhook-retry.log18 lines

Generating