Subscription and provisioning state model

Prerequisites and authority

Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.

Subscription and provisioning state model

For ordinary duration-based purchases, a new entitlement queues behind the active one. Activation sets its actual dates and starts its allowance/accounting period. The inspected activation service recalculates dates for queued subscriptions unless explicit dates were requested.

stateDiagram-v2
  [*] --> Queued: Ordinary purchase while active
  Queued --> Active: Prior entitlement ends
  Queued --> Cancelled: Supported cancellation
  Active --> Expired: Validity or quota boundary
  Expired --> [*]
  Cancelled --> [*]

This is an agreed simplified lifecycle, not an exhaustive enumeration of every source status. Explicitly dated administrator/import grants require separate policy/verification. Time plans expire by validity; usage plans by quota or validity, whichever comes first.

Payment success is independent from provisioning. A successful payment can link to a queued entitlement or to an active entitlement awaiting router repair. Preserve the economic result when a dependency fails.

At activation, the inspected service creates a fresh accounting segment for a still-connected physical session. Global quota must aggregate appropriate traffic across routers without overlapping live/stored accounting.

When diagnosing a lifecycle problem, distinguish quota exhaustion, queued activation, cancellation, explicit grants, router outages and profile changes. Preserve payment and subscription references before retrying an action; a status label alone does not prove that router provisioning completed.

Related guides

Related guides: Configuration reference (env vars, ports, URLs), Docker services, Compose files and persistent volumes, Database diagnostics and safe query reference.