Skip to content

not_found ​

The addressed thing does not exist, or does not exist for this caller.

StatusTitletype
404Not foundhttps://substrat.net/errors/not-found

What it means ​

Nothing answers at that address: no such record, route, operation or scope. On a multi-tenant surface this deliberately also covers two other cases. One is a thing that exists under another tenant. The other is an operation the install is not entitled to, where a 403 would confirm the feature exists. A client handles all of them the same way.

When it is returned ​

  • An id that names no record in this scope, or a record in the bin addressed by an operation that does not admit binned records.
  • An operation the vertical does not declare, or one the install is not entitled to.
  • A scope with no tenant record, on the control plane (reason: scope_unrecorded). A vertical's public edge answers a scope that is not serving with the router's own sentence instead, so a request that raced a suspension reads like one the router refused.

What it carries ​

  • reason: A slug the refusing module owns, narrowing the code. The platform's own are snake_case, but the wire does not enforce a grammar, so compare it as an opaque string. Branch on it; never show it.

Relayed from a scope store, it may also carry storeCode and storeBody. See the body for the members any problem may carry.

What to do ​

Do not retry. Check the id and the route. If the id came from a list, the record may have been deleted or binned since. Treat the thing as absent.

In /openapi.json ​

Documented on every operation's failure responses.

Every error code