Skip to content

Self-Test Superseded

URI: https://docs.ankatech.co/errors/self-test-superseded
HTTP Status: 409 Conflict

When you see this

An identity provider's self-test ran, but the provider changed while the connection test was in progress, so its result was not recorded. The test was made against a configuration or a secret the provider no longer holds: recording it would let the provider be enabled on a result that says nothing about its current configuration.

The self-test reads the provider, runs the connection test without holding the provider, and then reads it again. It records the result only when the configuration and the stored secret are still the ones it tested.

Common Causes

  • The provider's configuration was edited while the test ran, from another session or by automation.
  • Its secret was replaced, or its trust anchors were removed, while the test ran.
  • A quorum-approved change to the provider was applied while the test ran.
  • The provider's secret could not be read when the test started, and the secret store returned it again, or it was replaced, before the result was recorded: the failure was not the provider's.

Response Example

{
  "type": "https://docs.ankatech.co/errors/self-test-superseded",
  "title": "Self-Test Superseded",
  "status": 409,
  "detail": "The identity provider changed while its self-test ran, so the result was not recorded. Run the self-test again.",
  "instance": "/api/v3/admin/platform/idp/6b1d9f30-2c47-4e8a-b5d1-90fe3a72c418/test",
  "timestamp": 1785261989,
  "extensions": {
    "requestId": "2f6d8a41-9c3b-4e17-8a52-6b0e1d7c9f34"
  }
}

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

The attempt is recorded in the administrative audit trail as a self-test whose result was not recorded, with the result the test reached. A provider deleted while its test ran is answered 404 and recorded the same way.

How to Resolve

  1. Read the provider again to see its current configuration.
  2. Run the self-test again. Its result is recorded when nothing changes the provider while it runs.
  3. Enable the provider once a self-test of its current configuration has passed.

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