frozen: The stream is frozen

The stream or one of its ancestors is frozen, or the deployment is paused by the main switch (its open streams are held, and no new root stream opens). New spending, and a new allowance credential for the stream, is refused until it is thawed or the main switch resumes; work already signed or reserved stays settleable.

What to do

On the wire

HTTP 409, error type halted.

A client that does not send Dynamo-Error-Detail: 1 to a 1.3.0 route sees the legacy reason revoked, so its response shape is unchanged. Opted-in clients and the 1.4.0 routes see frozen.

A payment authorization (POST /owner/v1/streams/{id}/payment-authorizations) asked for while the main switch is paused answers reason: "main_switch_paused" with errorDetail.code frozen; nothing is authorized.

With Dynamo-Error-Detail: 1:

{
  "error": "halted",
  "reason": "frozen",
  "streamId": "stm_…",
  "detail": "…",
  "errorDetail": {
    "type": "halted",
    "code": "frozen",
    "message": "…",
    "param": null,
    "doc_url": "…/errors/frozen.md",
    "fix": "the stream or an ancestor is frozen; the owner thaws it, or it thaws at the freeze's expiry"
  }
}

See all error codes.