Subscription events store JSON states; billing steps run one row per transaction

Shipped

October 22, 2026 at 10:58 PM UTC

Author

Kamo

Commit

f92e25d

**************** are jsonb, and every caller wrote a bare status like ACTIVE - an invalid JSON insert that rolled back whatever it was auditing (order activation, renewal, the billing job's first run). A value that is not already JSON is stored as {"status": value}. The billing job's steps (prepareNext, rollOne, markOverdueIfLate) now take one subscription or invoice per transaction, so one failure cannot roll back every other customer's invoice.