Errors

When Teral can't complete a request, the response carries an error code such as err:teral:data:app_not_found. Every code has a page here, at a URL made from the code: /errors/teral/data/app_not_found.

The code has four parts: err, the system that raised it, a category, and the specific error. The system tells you where to look:

In API responsesCopy Anchor Link

API errors come as JSON. type links to the error's page here:

{
  "meta": { "requestId": "req_2v8…" },
  "error": {
    "title": "Not Found",
    "detail": "The requested app does not exist.",
    "status": 404,
    "type": "https://docs.teral.dev/errors/teral/data/app_not_found"
  }
}

In responses from your app's URLsCopy Anchor Link

When the gateway can't hand a request to your app, it answers itself. Browsers get an error page with the code, a link to its page here, and a request ID. Clients that ask for JSON get:

{
  "meta": { "requestId": "req_2v8…" },
  "error": {
    "code": "err:frontline:capacity:no_running_instances",
    "message": "No running instances are available to handle this request."
  }
}

Errors your app itself returns pass through unchanged.

Getting helpCopy Anchor Link

Include the request ID when you contact support@teral.dev. It lets us find the exact request.

All errorsCopy Anchor Link

GatewayCopy Anchor Link

Codes starting with err:frontline:.

APICopy Anchor Link

Codes starting with err:teral:.

RequestCopy Anchor Link

Codes starting with err:user:.