Errors
plan-limit-reached
A limit of your organization's plan was reached; `limit`, `max` and `used` say which.
403 Forbidden · Plan limit reached · type: https://docs.dlogify.com/errors/plan-limit-reached
When it happens
- Creating a project, an API key, a channel or inviting a member would go over the plan's maximum.
- A digest interval shorter than the plan allows was requested.
- A live tail was opened while the organization already had as many live tail sessions open as its plan allows.
How to fix it
Free up one (revoke an unused key, delete a channel or project, remove a member, close a live tail in another tab) or move to a plan with a higher limit (see Plans and usage). The body tells you which limit applies:
| Member | Meaning |
|---|---|
limit | projects, keys_per_project, members, channels_per_project, min_digest_minutes, tail_sessions or retention_days |
max | The plan's maximum; for min_digest_minutes, the shortest interval allowed |
used | How many are in use; for min_digest_minutes, the interval you requested |
Example
HTTP/1.1 403 Forbidden
Content-Type: application/problem+json{
"limit": "keys_per_project",
"max": 3,
"used": 3,
"type": "https://docs.dlogify.com/errors/plan-limit-reached",
"title": "Plan limit reached",
"status": 403,
"detail": "The plan allows 3 keys per project; 3 in use.",
"instance": "req_01j…"
}