Subscription standing

The Lifecycle

Transitions Explained

A valid subscription begins taking eligible changes. Administrators, access withdrawal or repeated dead deliveries can pause new fan-out. Resume requires current eligibility and does not reconstruct skipped changes; removal deletes configuration while retaining delivery history.

What Cannot Happen

New subscriptions start active after their configuration validates. Automatic failure pausing is conditional on active subscription status.

Concurrency and Timing

Versioned edits protect administrative subscription changes. Acceptance withdrawal pauses subscriptions inside installation edits. Installation suspension leaves subscription status unchanged while preventing new fan-out, and resumption does not backfill skipped changes.