Skip to content

Dependency Not Ready

URI: https://docs.ankatech.co/errors/dependency-not-ready
HTTP Status: 503 Service Unavailable

When you see this

An operator action was refused because a backing dependency the action needs is reported DOWN by the service's boot-dependency registry.

On the platform projection republish endpoint this is Redis: with Redis down there is nothing to publish the projections to, so the request is refused rather than accepted with a re-drive that could not do anything. A false acceptance would tell the operator the recovery ran when it did not.

Common Causes

  • Redis is down, unreachable, or still starting up.
  • A network partition between the service and Redis.
  • Credentials or TLS material for the dependency are wrong, so the connection never establishes.

Response Example

{
  "type": "https://docs.ankatech.co/errors/dependency-not-ready",
  "title": "Service Unavailable",
  "status": 503,
  "detail": "Redis is unavailable; the projections cannot be re-driven right now."
}

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. Check the dependency named in the detail and bring it back up.
  2. Confirm the service sees it as healthy again — the readiness probe reports the boot dependencies.
  3. Re-issue the operator action once the dependency is up.

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