Quota errors

Operade applies workspace-level daily model-cost limits. A zero limit has a separate meaning from an exhausted active limit so users receive an accurate recovery instruction.

Symptom#

A new conversation or next model-backed turn is rejected, Test Chat closes before producing a response, or a Telegram message ends quietly when the workspace cannot spend more on model usage.

Cause#

workspace_not_activated means the workspace limit is zero and has not been enabled for model use. quota_exceeded means the active workspace reached its daily usage limit. The daily boundary resets at 00:00 UTC. The check applies across agents in the workspace, not to only the agent currently open.

Verify#

Open Workspace Usage and compare today's total with the configured daily limit. Confirm whether the code indicates activation or exhaustion. Check the UTC boundary rather than assuming local midnight. Existing non-model dashboard reads may still work; the restriction applies when a conversation needs another model request.

Recovery#

For an inactive workspace, contact Operade through the approved support channel. For an exhausted limit, wait until the UTC reset or have the workspace owner coordinate the appropriate limit change. Do not create repeated conversations to bypass the check; all agents share the workspace budget.

Escalation#

Escalate when Workspace Usage shows capacity but a new conversation still receives a quota code. Include workspace identifier, UTC time, shown total and limit, and the code; do not include conversation content. See Usage and quota, Support, and Availability and limits.

Error code index#

• quota_exceeded — the workspace reached its active daily usage limit.
• workspace_not_activated — the workspace daily model limit is zero.

Quota recovery does not alter conversations that already ended. Start a new conversation after capacity becomes available.