Skip to content

Alert Test Rate Limited

URI: https://docs.ankatech.co/errors/alert-test-rate-limited
HTTP Status: 429 Too Many Requests

When you see this

This alert destination was tested too recently. The minimum interval between tests of the same destination is sixty seconds. The limit is per destination rather than per caller: the load it bounds lands on the recipient, and two administrators testing the same webhook is the same flood. A refused attempt does not push the window forward, so waiting out the interval always clears it.

Common Causes

  • Clicking the test button again within a minute of the previous test of the same destination.
  • Two administrators testing the same destination inside the same one-minute window.

Response Example

{
  "type": "https://docs.ankatech.co/errors/alert-test-rate-limited",
  "title": "Alert Test Rate Limited",
  "status": 429,
  "detail": "this destination was tested too recently; retry shortly",
  "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. Wait a minute from the last successful test of this destination and try again. Retrying inside the window costs nothing but will be refused again.
  2. Check whether another administrator has just tested the same destination — the previous test's verdict is already recorded on it.
  3. Testing a different destination is unaffected; the window is held per destination.

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