Errors
op_quota_exceeded
429 — the calling account has exhausted a monthly resource quota and cannot create more of the affected resource until the quota resets or is increased.
Last updated
Cause
Some Matter resources are gated by monthly account-level quotas — entity creations, formation submissions, and certain provider-backed actions. op_quota_exceeded fires when the account has consumed its full allowance for the current billing month and a new request would push it over. Unlike the request rate limit, this is a hard ceiling on resource creation, not on request frequency: backing off in time does not help.
The quota refills automatically at the start of each billing month. Increases above the default ceiling are available on higher plan tiers or by contacting the account team. The exact remaining count is visible in the dashboard usage report and via the getUsage operation.
Fix
- Read
getUsageto confirm which quota is exhausted and when it resets. - If the operation can wait until the next billing month, queue it for that date and surface the wait to the caller.
- If the operation is urgent, request a quota increase from the dashboard or the account team. Quota increases take effect within minutes.
- For agent-driven workloads, consider whether the rate of resource creation is intentional. Bursty creation may indicate a runaway loop rather than a need for a higher quota.
Related codes
op_rate_limit_exceeded— short-window request rate, not a monthly quota.op_service_degraded— the platform is shedding load.