Errors & Troubleshooting
Error code reference
Common error codes and families, safe next steps, and help with unlisted responses.
This lookup covers common codes and code families. The filter matches codes, names, and descriptions; it is not an exhaustive list of every endpoint response.
| Code | Kind | What it means & what to do |
|---|---|---|
internal_error | Error | Unexpected server error The native runtime returns this code with HTTP 500 when an unexpected failure prevents a normal response. Keep the correlation ID and safe message. Before repeating a write, reload the current records and review whether it already took effect; use Getting help if the outcome is unclear. |
empty_location_scope | Error | No active authorized locations An assigned location is inactive or no longer belongs to this organization. The user's location scope is denied until an organization admin assigns an active location or reviews the user's scope. CompanyIQ, OpsAtlas and Developer AI return HTTP 403 with a correlation ID; retrying without a scope change will not help. |
51005 | Error | AI assistant daily action quota reached The user's assistant hit its per-day action budget. Further actions queue until the daily reset. Builders can review per-user quotas in assistant settings. |
51000–51999 | Error | Request validation failed (builder console) The request was well-formed but not valid — a missing field, a bad value, or an operation the current state doesn't allow. The message names the specific problem. Returned as HTTP 400. |
55000–55099 | Blocked | Account lifecycle state blocks the action The account's state — unverified email, trial expired, past due, suspended, or locked — prevents this action. Resolve the state in the console (verify email, update payment) and retry. Returned as HTTP 423. |
55100–55199 | Error | Authentication or session failure Sign-in failed, the token is expired or revoked, or an MFA step is required. Refresh once; if that fails, sign in again. Returned as HTTP 401. |
57100–57599 | Error | Marketplace operation refused A marketplace action failed a rule: missing store or payout permission, a product/offer not in the right state to activate, a price that doesn't match the billing model, or a payout exceeding the available balance. The message names the specific requirement — meet it and retry. |
E003–E007 | Error | Page content structure invalid The page document violates a structural rule — an unknown block type, a malformed property, or content the renderer can't accept. The editor lists each finding with its block; fix the listed blocks to unblock saving. |
E021 | Blocked | Block identity would be lost A raw JSON edit removes or duplicates a block's stable identity, which future template upgrades rely on to merge safely. Cancel and restore the identity, or acknowledge to proceed — acknowledged blocks are treated as brand-new content in all future upgrades. |
W104–W105 | Blocked | Page content warning A draft may be saved with warnings, but the current tenant page publication gate requires zero errors and zero warnings. Review the validation report and resolve these findings before publishing. |
429 + retryAfterSeconds | Blocked | Rate limited Too many attempts in the window (for example, 10 sign-in failures in 15 minutes). Wait the number of seconds indicated, then retry. Hammering extends nothing. |
Reading a code
Responses may use named or numeric codes. Page-content reports also use E-codes for errors and W-codes for warnings. Saving a draft and publishing are separate checks; the tenant page publication gate requires both errors and warnings to be resolved. Use the HTTP status and safe message from the actual response; a code alone may not identify the cause. When contacting support, include the exact code and correlation ID when present.
When a code is not listed
Use Getting help with the exact code, safe message, HTTP status, and correlation ID when provided. If a write was not confirmed, reload and review the current records before submitting another write. Do not assume that a failed response means nothing changed.
Capability review: 2026-09-14. See current features and setup requirements, the generated API Map and first-class module inventory.