Workspace is suspended
Diagnose a workspace suspension banner, 503 responses, and blocked deployments.
A suspended workspace cannot serve traffic or create deployments for any of its projects. Suspension is a platform action (billing, usage, terms, or admin). Workspace owners cannot clear suspension themselves; only platform admins can unsuspend.
Symptoms
You may see one or more of the following:
- A workspace banner that says the workspace is suspended
- HTTP
503on production and preview hostnames - Response header
x-easel-serve-denied: WORKSPACE_SUSPENDED - Deploy or CLI errors with code
WORKSPACE_SUSPENDED
What is blocked
While the workspace is suspended:
- Every project’s production and preview traffic is denied at the edge.
- New deployments (production and preview) fail the deploy gate.
- Project pause and resume are rejected until the suspension is cleared.
Git pushes that would create deployments are skipped for the same reason.
What to do next
Use the banner reason to choose the next step:
| Reason | Meaning | Next step |
|---|---|---|
billing_unpaid | Unpaid balance | Open Billing for the workspace |
usage_exceeded | Plan usage limits | Open Billing and reduce usage or upgrade |
tos | Terms of service issue | Open Workspace settings and contact support |
admin | Manual platform action | Open Workspace settings and contact support |
If the banner points at billing, settle the account there. Platform admins clear suspension with the admin suspend controls. That path is not available to workspace members.
Pause vs suspend
Project pause is owner-controlled and production-only. Preview keeps working. See Pause and resume a project.
Workspace suspend is platform-enforced and applies to all targets. Suspend wins if both flags are set.
Edge timing after unsuspend
Manifest cache on the edge is 30s by default. After an admin unsuspends the workspace, wait up to that TTL before expecting successful responses again.