Error Notifications

Errors can occur when navigating data. They can be caused by bad requests (e.g. a request for a resource that doesn't exist), connection issues (e.g. a database has gone offline), or if the SlashDB service times out (e.g. if all workers are occupied), to give a few examples. When that happens, SlashDB will display an error page.

Info

Learn more about Handling Responses using SlashDB.

E.g. visiting this URL produces an HTTP 404 error:

/db/Chinook/Invoice/InvoiceId/1000.html

Errors are also returned in JSON, XML, and CSV formats when accessing endpoints in those formats causes an error.

JSON Error

/db/Chinook/Invoice/InvoiceId/1000.json

{
  "http_code": 404,
  "description": "The resource could not be found."
}

XML Error

/db/Chinook/Invoice/InvoiceId/1000.xml

<SlashDB>
  <http_code>404</http_code>
  <description>The resource could not be found.</description>
</SlashDB>

CSV Error

http_code,description
404,The resource could not be found.

Response Header

Errors are always included in the Warning response header:

HTTP/1.1 404 Not Found
Content-Length: 155
Content-Type: text/xml; charset=utf-8
Date: Mon, 05 Apr 2025 14:24:35 GMT
Server: waitress
Warning: The resource could not be found.