Error codes

When a bot cannot answer because of a technical or configuration problem, visitors see a short error code instead of the private reason. Your team can look up that code in Dashboard > Chatbot > Error codes.

How to use a code

• Ask the visitor or agent for the exact code
• Open the bot's Error codes page and search the code
• Check the internal reason, route, session, conversation link, and metadata
• Fix the bot setting, embed, billing state, or integration shown by the log

Code families

• BOT-EMPTY: the visitor sent a blank message
• BOT-TOOLONG: the message was over 2,000 characters
• BOT-REQUEST: the request is malformed or missing a required field
• BOT-404: the widget or API points to a bot that cannot be found
• BOT-PAUSED: the bot is switched off and is not serving replies
• BOT-RATE: too many requests hit the public endpoint in a short burst
• BOT-LIMIT: this conversation reached its per-chat message cap
• BOT-QUOTA: the plan ran out of included conversations and credits
• BOT-CONFIG: a required provider, model, or setting is missing
• BOT-KEY: the AI provider key is missing or was rejected
• BOT-AI: the upstream AI provider errored or was overloaded
• BOT-TIMEOUT: the reply took too long and timed out
• BOT-TOOL: an action or integration the bot ran failed
• BOT-DATA: a database or storage operation failed
• BOT-RUNTIME: an unexpected internal error not covered above

What visitors see

Visitors only see a generic message plus the code. They do not see stack traces, bot existence checks, API details, provider errors, or private configuration names.

History

The dashboard stores customer-facing bot errors from the moment error-code logging is enabled. Errors that happened before logging existed cannot be reconstructed retroactively.