Skip to content

Projection Re-Drive Unavailable

URI: https://docs.ankatech.co/errors/projection-redrive-unavailable
HTTP Status: 503 Service Unavailable

When you see this

The executor that runs the projection re-drive off the request thread could not accept the work, so nothing was started.

This is distinct from a re-drive that is already running, which answers 409. Here there is no re-drive in progress — the asynchronous worker itself is not in a state to take the submission.

Common Causes

  • The service is shutting down, so the executor no longer accepts submissions.
  • The executor has been stopped, or its queue is saturated.
  • The request arrived during a window where the service was not fully started.

Response Example

{
  "type": "https://docs.ankatech.co/errors/projection-redrive-unavailable",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "The projection re-drive executor is unavailable; retry shortly."
}

Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.

This endpoint builds its body from the framework's problem type directly, so it carries the five RFC-defined members only. It has no timestamp and no extensions block, and instance is not populated.

How to Resolve

  1. Retry shortly — nothing was submitted, so the retry is safe.
  2. If the service is restarting, wait for it to report ready and retry then. The boot-recovery hook re-drives the projections on startup through the same driver, so the work may already be done.
  3. If it persists past a restart, check the service logs for the executor's state before triggering further republishes.

For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.