Troubleshooting your organization and plan

#403 PLAN_LIMIT_REACHED, PLAN_QUOTA_EXHAUSTED or PLAN_FEATURE_REQUIRED

• Cause: A plan limit or monthly quota is used up, or the feature isn't in your plan. The body names the limit_key, the limit, what is used and the required_plan.
• Check: Organization › Usage, and the key in Plan limits.
• Fix: Upgrade, add an add-on where one exists, or wait for resets_at (Billing, invoices and overage).
• Verify: The same request succeeds.

#An invitation can't be accepted

• Cause: The link is older than 7 days; the person signed in with a different email; their email isn't verified yet (EMAIL_NOT_VERIFIED); the organization only accepts certain email domains (EMAIL_DOMAIN_NOT_ALLOWED); or the plan's member seats are full.
• Check: The email the invitation was sent to, and Organization › Team › Invitations.
• Fix: Invite again (sends a fresh link), sign in with the invited address and verify it, or free a seat (Organizations, members and roles).
• Verify: The person appears under Team with their role.

#A member gets 403 in the console or CLI

• Cause: Their role doesn't include the permission (for example only owners and admins invite members or create projects), or they were removed.
• Check: Organization › Team: their role, and the role's permissions.
• Fix: Give them a role with that permission, or a custom role (Working as a team).
• Verify: They can do it after reloading the console.

#An API key suddenly returns 401

• Cause: The key was rotated or revoked, has expired, or belongs to another project.
• Check: Project settings › API keys: whether the key is still listed, when it expires and when it was last used.
• Fix: Create or rotate a key, deploy the new value, then revoke the old one (API keys).
• Verify: Requests with the new key succeed and the old key's last use stops moving.

#The browser reports a CORS error, or 403 ORIGIN_NOT_ALLOWED

• Cause: The site's origin (scheme, host and port) isn't in the project's allowed origins.
• Check: The Origin header in the browser's network tab against Project settings › API › Allowed origins.
• Fix: Add the exact origin, or a pattern such as https://*.example.com (Allowed origins (CORS) for browser apps).
• Verify: Reload; the request succeeds.

#Still stuck?

Email outreach@sovaria.in with your project URL, the time it happened (with time zone), the X-Request-ID response header or the trace_id from the error body, and your organization id. Never send keys, passwords, tokens or your users' data.