Internal Server Error

internal-error · 500

Something failed on our side, and the request may or may not have taken effect.

A 500 says the server didn't finish cleanly, not that it did nothing. In production detail is the same sentence every time; the specifics are in our logs, under this response's requestId.

This type adds no members to the ones every error carries.

Common causes

  • A defect in the service.
  • A dependency the service needs behaved unexpectedly.

How to fix the call

  • Keep requestId. It is the one value that finds this exact failure, so quote it when you report the problem.
  • Retry once, after a delay. If it fails again, stop rather than loop.
  • Before retrying a write, read the resource back. The first attempt may have partly applied.
  • Don't report a deploy as successful because a retry returned 200: check the build log.

Example response

json
{
  "type": "internal-error",
  "title": "Internal Server Error",
  "status": 500,
  "detail": "An unexpected error occurred. Please try again later.",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "method": "POST",
  "instance": "POST /v1/projects/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/services",
  "docs": "https://ghaym.me/docs/errors/internal-error"
}