Log Store Unavailable

logs-store-unavailable · 503

The store that keeps the service's past logs couldn't be read, so the API returned no search results rather than an empty page.

The live tail beside it keeps streaming: ghaym cloud services logs <service> reads the tail and never the store. detail names what went wrong, in brackets.

Besides the members every error carries, this type adds code.

Common causes

  • The store didn't answer within the search's time limit.
  • The store answered with an error status, which detail names.
  • No log store is set up for the sites the service runs in.

How to fix the call

  • Retry the search after a short wait.
  • Meanwhile, read what is happening now from the live tail.
  • If detail says no log store is configured, tell the user: retrying won't help.

Example response

json
{
  "type": "logs-store-unavailable",
  "title": "Log Store Unavailable",
  "detail": "The log store could not be read (the store answered 502), so this service's stored history is unavailable. The live tail is unaffected; try the search again shortly.",
  "code": "logs_store_unavailable",
  "requestId": "req-1785231000000-4f7b2c9ae",
  "timestamp": "2026-07-28T09:30:00.000Z",
  "path": "/v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/logs/query",
  "method": "GET",
  "instance": "GET /v1/services/0199e0a3-6f21-7c4a-9d18-2b7c5f3ad401/logs/query",
  "status": 503,
  "docs": "https://ghaym.me/docs/errors/logs-store-unavailable"
}