Alert Destination Changed During Test
URI: https://docs.ankatech.co/errors/alert-destination-changed-during-test
HTTP Status: 409 Conflict
When you see this
A platform administrator tested an alert destination (POST /api/v3/admin/platform/alerts/destinations/{destinationId}/test, operation testPlatformAlertDestination), and the destination was saved while the test delivery ran. Any save counts, whatever it changed, even one that changed nothing.
The test delivery was attempted and cannot be undone. Its verdict describes the configuration that was replaced, so it is neither recorded on the destination nor returned, and the replacement stands as it was committed. The attempt is recorded in the platform audit trail as a failed test, naming the verdict it measured.
Common Causes
- Another administrator edited the destination while the test was running.
- The destination was edited and tested at almost the same time, for example from two console tabs.
A destination accepts one test a minute. A test run again within that minute is refused as too many requests; wait for the minute to pass.
A test against a slow or unreachable recipient waits for the delivery's own timeout, which widens the window in which an edit lands during it.
Response Example
{
"type": "https://docs.ankatech.co/errors/alert-destination-changed-during-test",
"title": "Alert Destination Changed During Test",
"status": 409,
"detail": "A test delivery was attempted, but the destination's configuration changed during the test, so its verdict was not recorded. Test the destination again.",
"instance": "/api/v3/admin/platform/alerts/destinations/3f6c2a9e-8b1d-4e7a-9c52-0d4b7e1a6f38/test",
"timestamp": 1763112600,
"extensions": {
"requestId": "7c2e9b4a-1f6d-4a83-b5e2-9d0c3f7a1e64"
}
}
Content-Type: application/problem+json — the response follows RFC 9457 Problem Details.
How to Resolve
- Read the destination (
GET /api/v3/admin/platform/alerts/destinations) to see the configuration that is now in place. - Test it again. The recorded verdict then describes the configuration you tested.
A replace clears a destination's last test, so after any edit the destination shows no verdict until it is tested again.
For full schema definitions, examples, and interactive testing, see the Developer Hub Reference.