Skip to main content

quota-exceeded

HTTP status: 403 Forbidden Type URI: https://docs.evinor.ai/problems/quota-exceeded

The account has reached a plan quota for the resource it is creating or growing. The request itself is valid; the account just has no room for it under its current plan. When the quota is a known one, detail names the limit (for example, "You've reached your limit of 5 beats.").

This is different from not-entitled, which means the account cannot use the feature at all, and from missing-scope, which is fixed on the key.

Common causes​

  • Creating a beat (POST /v1/beats) when the account already holds as many beats as its plan allows.
  • Creating or replacing a beat with more clauses than the plan allows per beat.

How to resolve​

Retrying the same request will not succeed. Make room — delete a beat you no longer need, or send fewer clauses — or move the account to a plan with a higher quota. See Beats.