Error Code Categories (MMEE)
Errors shown in Error Logs follow an internal code categorization system, nicknamed MMEE (grouping by Module/Error reason). Every logged error carries a code from this categorization.
Note
⚠️ Note from the documentation team: the table below lists the categories confirmed so far. The full set of codes (all ~28 internal categories) still needs to be validated and completed by the product/engineering team before this page can be considered a definitive reference — the goal here is to record the structure so that the full fill-in is done directly by whoever has access to the categorization source code.
Code structure
In general, each error category is tied to a functional area of NicoChat, for example:
Area
Examples of errors that fall into it
Message sending (channel)
failure to deliver a message due to the 24-hour window limit, invalid number, disconnected channel
External integrations (API/External Request)
timeout, 4xx/5xx error from the third-party service, response in an unexpected format
AI (AI Agents/Tasks/Functions)
AI provider error, token limit exceeded, API key authentication failure
E-commerce
failure to create/update an order, nonexistent product/variant, checkout error
Webhooks and triggers
invalid payload received, failure to process a configured trigger
How to use this in practice
When you open an error in Error Logs, check the error type/code before investigating the specific node — this helps you quickly tell whether the problem is on the NicoChat side, on an integrated external service, or in the flow's own configuration.
If you find a code that is not documented here, add it to this page (or report it to whoever maintains this documentation) so we can keep completing the table over time.