kapi WorksDocs
Errors

writer_unavailable

History catching up. HTTP 503.

What it means

Recent changes are still being recorded. Try again shortly.

What to do

Retry after Retry-After seconds. A pull already in progress can still finish from its cursor.

Headers

A 503 response also sends Retry-After.

Example response

{
  "type": "https://docs.kapiworks.com/errors/writer_unavailable",
  "title": "History catching up",
  "status": 503,
  "detail": "Recent changes are still being recorded. Try again shortly.",
  "code": "writer_unavailable"
}

Errors use application/problem+json (RFC 9457). Act on code or type; detail is for people and can change. See every code.