Skip to content

Probe Address Not Resolvable

URI: https://docs.ankatech.co/errors/probe-address-not-resolvable
HTTP Status: 500 Internal Server Error

When you see this

A delivery-provider probe was asked to test a provider position whose address does not resolve to any configured provider. The address comes from a row the control plane had already loaded and was about to write a verdict against, so an empty resolve is a platform inconsistency rather than a fact about the relay. It is deliberately not a 4xx and deliberately not a verdict: recording it as a failed probe would demote an active provider row and take a working relay out of service for a transient internal fault.

Common Causes

  • The provider row the probe was asked about no longer resolves at the named channel and position.
  • The provider chain changed between the moment the row was loaded and the moment the probe ran.
  • An internal inconsistency between the stored provider configuration and the resolved delivery chain.

Response Example

{
  "type": "https://docs.ankatech.co/errors/probe-address-not-resolvable",
  "title": "Probe Address Not Resolvable",
  "status": 500,
  "detail": "The provider address under test did not resolve. This is a platform inconsistency, not a verdict about the provider, and no verdict has been recorded.",
  "instance": "/internal/s2s/notification/providers/probe"
}

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

How to Resolve

  1. Do not treat this as a provider failure. No verdict was recorded and the provider's existing status is unchanged.
  2. Re-read the tenant's delivery-provider chain and confirm a provider is configured at the channel and position you are testing, then probe again.
  3. If it persists, the address the probe was given and the position that failed to resolve are in the notification service's own log; the body carries neither by design. Callers of this internal endpoint see the fault re-presented as a 502 naming the notification service by role.

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