Error codes
Imperal Cloud error codes — what each code means, when it fires, and how to fix it, with examples for validation, confirmation, tenant, and runtime errors.
Errors in Imperal Cloud always have a code (uppercase, snake-case). Codes are stable — you can match against them in clients without parsing prose. This page is the reference.
Lifecycle errors
Build / publish errors
Runtime errors
How errors render to chat
The web-kernel renders errors via i18n templates — never raw Python exceptions. The platform always surfaces a friendly, localized message instead of a stack trace:
| Code | Template (English) |
|---|---|
VALIDATION_MISSING_FIELD | "I had trouble understanding the field — could you re-state what you want?" |
FABRICATED_ID_SHAPE | "I don't have a record of that — could you try rephrasing?" |
TENANT_SCOPE_VIOLATION | "That's not yours — this account doesn't have access." |
INTERNAL | "Something went wrong on our side. The team's been notified." |
Your tool can return {"error": {"code": "...", "detail": "..."}} and the web-kernel will render it consistently.
Where to next
Glossary
Every Imperal Cloud and Webbee term defined — one alphabetical entry per term, from ICNLI to web-kernel. Decorators, error codes, and federal concepts.
FAQ
Imperal Cloud & Webbee FAQ — quick answers on building extensions, ICNLI, Python support, permissions, security, pricing, and the federal contract model.