Whether a catalog object or customer reached Stripe is recorded in two places #183

New Issue

2026-10-06T21:25:13Z

cgalo5758 commented

2026-10-06 21:25:13 +00:00

Pushed products, prices and customers have a mapping with sync_status (pending, synced, stale) and outbox rows. When the outbox gives up, its row is dead_letter and the mapping stays pending. SyncProductToStripe (internal/server/operator_billing.go) searches core.outbox by JSON payload fields and retries with hand-written SQL; the readiness panel runs the same search. Nothing retries a customer.

Done when: one stored state says pending, synced or failed per object; retry is a query of the outbox's package, as RequeueDesiredState is in internal/integration; and the panel reads one place. Related: #80.

Pushed products, prices and customers have a mapping with `sync_status` (`pending`, `synced`, `stale`) and outbox rows. When the outbox gives up, its row is `dead_letter` and the mapping stays `pending`. `SyncProductToStripe` (`internal/server/operator_billing.go`) searches `core.outbox` by JSON payload fields and retries with hand-written SQL; the readiness panel runs the same search. Nothing retries a customer. Done when: one stored state says pending, synced or failed per object; retry is a query of the outbox's package, as `RequeueDesiredState` is in `internal/integration`; and the panel reads one place. Related: #80.

cgalo5758 added the

kind

design

area/billing area/integrations labels 2026-10-06 21:25:13 +00:00

cgalo5758 referenced this issue

2026-10-06 21:26:09 +00:00

The operator cannot see which payment-provider product a catalog product is mapped to #100

Sign in to join this conversation.