More reliable subscription renewals

Usage statements now handle first billing cycles, interrupted operations and unclassified failed builds without holding up a renewal.

  • Billing

Read as Markdown ↗

Subscription renewals now measure usage from the moment paid coverage begins, including the first cycle after Checkout, cancellations and trial transitions. API-created subscriptions are aligned to calendar-month boundaries in UTC, matching subscriptions created through Checkout.

An unclassified failed build is priced at zero instead of blocking the entire invoice. Interrupted metering operations that were superseded by a later successful operation no longer hold a renewal in draft, and webhook failures are reported for investigation.

← All releases