change_frozen
HTTP status: 423 Locked
A change freeze covers the environment the request would change, and the request is refused. Nothing was written. Reads and flag evaluation are never refused.
A change to one environment is refused when a freeze covers it. A change that reaches every environment in a project, such as deleting the project, is refused when a freeze covers any of its environments. The error’s change_freeze object says which window is responsible.
Common causes
Section titled “Common causes”- A scheduled freeze window has started, or someone used Freeze now.
- A script or CI job that worked yesterday now changes flags in an environment a freeze covers.
- The request sent
X-Freeze-Override: truebut the caller isn’t an Owner or Admin. The error then carriescan_override: false. - The override header was sent without an
X-Intent-Reason.
How to fix
Section titled “How to fix”- Wait until the freeze ends.
change_freeze.ends_atsays when. It isnullfor an open-ended freeze, which lasts until someone ends it. - If the change can’t wait and the caller is an Owner or Admin (
can_override: true), retry the same request with bothX-Intent-ReasonandX-Freeze-Override: true. One override covers one request, and it is recorded in the audit log. - Otherwise ask an Owner or Admin to make the change or to end the freeze.
- From the MCP server, an Owner or Admin passes
freeze_override: truewithreasonon the write tool.
Example
Section titled “Example”{ "error": "change_frozen", "message": "Environment 'production' is frozen by the change freeze 'Black Friday code freeze' until 2026-11-30 06:00 UTC. An Owner or Admin can break the freeze by sending an X-Intent-Reason and X-Freeze-Override: true.", "change_freeze": { "id": "6f1c1f0e-5d6e-4c58-9a3b-0d3a5a1d2e11", "name": "Black Friday code freeze", "environment_key": "production", "ends_at": "2026-11-30T06:00:00Z", "can_override": true }, "docs_url": "https://featureflip.io/docs/management-api/errors/change_frozen"}