Skip to content

Alert Test Unavailable

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

When you see this

The destination test could not run because no outbound delivery path is bound in this build. This is checked before the rate-limit window is claimed, so an unavailable test costs you nothing and does not lock you out of re-checking. No verdict is recorded: storing one would make an unavailable feature indistinguishable from a working one when the destination list is read back.

Common Causes

  • The build or deployment does not have the outbound alert delivery path wired.
  • The delivery component is not present in this environment.

Response Example

{
  "type": "https://docs.ankatech.co/errors/alert-test-unavailable",
  "title": "Alert Test Unavailable",
  "status": 503,
  "detail": "the outbound delivery path is not available in this build",
  "instance": "/api/v3/admin/platform/alerts/destinations/7c9e6679-7425-40de-944b-e07fc1f90ae7/test",
  "timestamp": 1730000000,
  "extensions": {
    "requestId": "550e8400-e29b-41d4-a716-446655440000"
  }
}

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

How to Resolve

  1. Confirm with the platform operator whether the outbound alert delivery path is deployed in this environment.
  2. Do not read this as a verdict about the destination — the destination was never contacted and its recorded verdict is unchanged.
  3. Retry once the delivery path is available. Repeated attempts while it is not do not consume the per-destination test window.

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