A product or price that Stripe makes after answering the console with a server error is never recorded from Stripe's event #314

New Issue

2026-10-31T03:37:01Z

cgalo5758 commented

2026-10-31 03:37:01 +00:00

What happens

The console records which Stripe product or price each of its own products and prices is; this record is its mapping. When the console asks Stripe to create a product or price, it puts its own id in the object's metadata (product_id or price_id).

The catalog sync specification (openspec/specs/stripe-product-catalog-sync/spec.md, the requirements on product.created and price.created) says that when Stripe's event for a new product or price arrives and the console has no mapping for that Stripe id, the console records the mapping. Today the event handlers log the object as possibly made outside the console and drop the event: they never read the console's id from the object's metadata, although the event the console stores keeps it.

Stripe can make an object after answering the console's create with a server error, for example while it recovers from an incident, and then sends that event. The console then never learns that the object exists.

What should happen

The handler reads the object's metadata product_id or price_id and records the mapping when the console's mapping for that product or price is still waiting for a Stripe id. A product or price the console already records with a Stripe id keeps that id. This is what Stripe advises after a server error: reconcile from its events by an identifier the integration put in the metadata.

Where

internal/integrations/stripe/workflows/webhook.go (handleProductEvent, handlePriceEvent)

Why it matters

A product Stripe made stays unrecorded, and cannot be bought, until an operator presses Find or create in Stripe on its page, although Stripe's event already named it.

Related: #312.

### What happens The console records which Stripe product or price each of its own products and prices is; this record is its mapping. When the console asks Stripe to create a product or price, it puts its own id in the object's metadata (`product_id` or `price_id`). The catalog sync specification (`openspec/specs/stripe-product-catalog-sync/spec.md`, the requirements on `product.created` and `price.created`) says that when Stripe's event for a new product or price arrives and the console has no mapping for that Stripe id, the console records the mapping. Today the event handlers log the object as possibly made outside the console and drop the event: they never read the console's id from the object's metadata, although the event the console stores keeps it. Stripe can make an object after answering the console's create with a server error, for example while it recovers from an incident, and then sends that event. The console then never learns that the object exists. ### What should happen The handler reads the object's metadata `product_id` or `price_id` and records the mapping when the console's mapping for that product or price is still waiting for a Stripe id. A product or price the console already records with a Stripe id keeps that id. This is what Stripe advises after a server error: reconcile from its events by an identifier the integration put in the metadata. ### Where `internal/integrations/stripe/workflows/webhook.go` (`handleProductEvent`, `handlePriceEvent`) ### Why it matters A product Stripe made stays unrecorded, and cannot be bought, until an operator presses Find or create in Stripe on its page, although Stripe's event already named it. Related: #312.

cgalo5758 added the

kind

bug

area/billing area/integrations labels 2026-10-31 03:37:01 +00:00

cgalo5758 referenced this issue from a commit

2026-10-31 03:46:57 +00:00

Stop a Stripe create Stripe answered with its own 500, and look it up before sending it again

cgalo5758 referenced this issue from a commit

2026-10-31 04:04:05 +00:00

Archive the unknown-create lookup change

Sign in to join this conversation.