# Revoked deploy tokens are refused even while token checks are unavailable

> If the control plane started while it couldn't reach its token store, uploads skipped the revocation and project checks. Uploads now wait with a retry message until tokens can be checked, and read-only credentials can no longer change domain mappings.

Date: October 1, 2026 · Type: Security · Products: CDN

Source: https://changelog.evolvingedge.ai/2026-10-01-revoked-deploy-tokens-always-refused/

Two checks on who may change a site didn't hold in every case. Both are fixed.

**Deploy tokens are always checked.** A deploy token is checked twice on every upload: that it hasn't been revoked, and that it belongs to the project being deployed to. Both checks read a token store. If the control plane started while that store was unreachable, uploads skipped both checks, so a revoked token, or one from another project, was accepted. An upload that can't be checked now waits: it's refused with a message to retry shortly, and nothing is written. Registering a new token does the same.

**Changing a domain needs write permission.** Creating a domain mapping already required permission to change domains, but changing or deleting one, and creating or changing a domain assignment, needed only permission to read them. Every one of those now requires write permission too.

## What you need to do

Nothing. If an upload is refused with "Deploy token checks are unavailable; retry shortly", run it again in a minute.
