Errors
infra_internal_error
500 — an unexpected platform error occurred; retry idempotently or contact support with the request_id.
Last updated
Cause
Matter returns infra_internal_error for any failure that is not modelled by a more specific code — an unhandled exception in a handler, a backend dependency throwing an unexpected error, an invariant inside the platform tripping. The platform's observability stack captures these with full context (request id, principal, route, stack), and they generate paging when their rate crosses thresholds.
This is the catch-all signal. By design, customer-facing surfaces are not told the specific internal reason — that would leak implementation detail and create coupling between the public contract and Matter's internals. The request_id on the response is enough for the support team to pull the full trace.
Fix
- Capture the
request_idfrom the response (theX-Request-Idheader and theinstancefield on the problem body). - Retry the operation idempotently. Use the original
Idempotency-Keyso a duplicate side effect is not produced if the original partially succeeded. - If the retry succeeds, treat the original as transient and move on.
- If the retry fails too, contact support and quote the
request_id. The on-call engineer can pull the full trace and explain what happened.
Related codes
infra_db_unavailable— the database, specifically.infra_kms_unavailable— the key-management service.op_service_degraded— deliberate load-shedding, not an unexpected error.op_provider_unavailable— a third-party provider is down.