Skip to content

Projection Re-Drive Already In Progress

URI: https://docs.ankatech.co/errors/projection-redrive-in-flight
HTTP Status: 409 Conflict

When you see this

A re-drive of the platform's Redis projections is already running, so this request was not started.

The manual republish endpoint and the boot-recovery hook share one driver and one in-flight flag by design, so a recovery re-drive and an operator republish never run concurrently. A second request coalesces onto the first rather than duplicating the work.

Common Causes

  • A second operator triggered a republish while the first was still running.
  • The endpoint was called again before the previous re-drive completed.
  • The service is still completing its boot-recovery re-drive.

Response Example

{
  "type": "https://docs.ankatech.co/errors/projection-redrive-in-flight",
  "title": "Conflict",
  "status": 409,
  "detail": "A projection re-drive is already in progress; retry after it completes."
}

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. Wait for the running re-drive to finish; it is bounded and runs off the request thread.
  2. Retry the republish afterwards if the projections still need it.
  3. Do not loop on retries — the in-flight re-drive is doing the work this request asked for.

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