Errors that bypass the { code, data } envelope or have no catalog entry yet. They are detected by shape or source rather than by a fixed number.
uncaught_exception Uncaught exception
Severity: error · Category: process · Detected via: process.on('uncaughtException')
A thrown error that was not wrapped in the { code, data } envelope.
Common causes
- Bug throwing outside a try/catch
- Unexpected runtime fault
Resolution
- Resolver reports it (report-only); existing crash behavior preserved
- Escalate to ops
Auto-fix: none · User-actionable: no · Related: unhandled_rejection
Source: process-level detector (2e)
unhandled_rejection Unhandled promise rejection
Severity: error · Category: process · Detected via: process.on('unhandledRejection')
A rejected promise that nobody caught.
Common causes
- Missing await/catch on an async call
Resolution
- Resolver reports it (report-only)
- Escalate to ops
Auto-fix: none · User-actionable: no · Related: uncaught_exception
Source: process-level detector (2e)
thrown_string_error Thrown string error
Severity: error · Category: envelope-bypass · Detected via: router global catch ~2075
A throw new Error(...) that surfaces as a 401/500 instead of a { code, data } body.
Common causes
- e.g. 'app is off', 'Account suspended', 'Account terminated' (router ~3400-3409)
Resolution
- Resolver triages from the message
- Escalate or notify per diagnosis
Auto-fix: none · User-actionable: no · Related: 401, 500
Source: router_module ~3400-3409
broker_failure Message broker failure
Severity: error · Category: broker · Detected via: ms_broker.mjs / msg_broker.mjs error paths
RabbitMQ disconnect, queue timeout, or message serialization error.
Common causes
- Broker down/unreachable
- Queue timeout
- Serialization error
Resolution
- Resolver reports it
- Check RabbitMQ health
- Escalate to ops
Auto-fix: none · User-actionable: no · Related: provider_outage
Source: common/ms_broker.mjs, common/msg_broker.mjs
unknown_code Unknown negative code
Severity: warning · Category: catalog-gap · Detected via: resolver lookup miss
A negative code with no catalog entry (new code shipped since the last catalog update).
Common causes
- New code added in a module but not yet documented here
Resolution
- Resolver writes a catalog_gap proposal for human review
- Add the code to this catalog
Auto-fix: none · User-actionable: no
Source: resolver (2e)
malformed_response Malformed response
Severity: error · Category: envelope-bypass · Detected via: resolver shape check
A response missing/zero code, non-object, or null data where data was expected.
Common causes
- Method returned the wrong shape
- Partial/short-circuited return
Resolution
- Resolver triages
- Fix the offending method to return { code, data }
Auto-fix: none · User-actionable: no
Source: resolver (2e)
provider_outage Upstream provider outage
Severity: error · Category: dependency · Detected via: ai_module report_ai_status error; DB connect failures
An external dependency (AI, DB, upstream service) is unavailable.
Common causes
- OpenAI/AI provider error
- CouchDB connect failure
- Upstream down
Resolution
- Resolver may retry transient ops
- Escalate if sustained
Auto-fix: retry · User-actionable: no · Related: -999, 502
Source: resolver (2e)
anomaly Error-rate anomaly
Severity: warning · Category: aggregate · Detected via: cron sweep aggregation (anomaly_threshold)
A signature repeats above threshold in the window, even with no single fatal error.
Common causes
- Spike of the same error signature
Resolution
- Resolver clusters and escalates the pattern to ops
Auto-fix: none · User-actionable: no
Source: resolver sweep (2e)