Skip to main content
General·HTTP 422·API, CLI, FE

Secret manager test failed

secret_source_test_failed

The secret manager didn't accept the connection, so nothing was saved.

What this means​

A secret manager is tested before it is connected, and before new settings or a new credential are saved. The test signed in and was refused, or couldn't reach it.

How to fix it​

Fix what errors[] (field test) says: the credential, what it may read, or the settings. Then save again.

Retry behavior​

Retry after fixing the credential or settings.

How it appears in the response​

ComputeSphere returns errors as RFC 7807 Problem Details. The type field is the docs URL for this page — switch on code in your client.

{
  "type":    "https://computesphere.com/docs/errors/secret_source_test_failed",
  "title":   "Secret manager test failed",
  "status":  422,
  "code":    "secret_source_test_failed",
  "detail":  "The secret manager didn't accept the connection, so nothing was saved.",
  "instance": "/v2/…",
  "request_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479",
  "trace_id":   null
}

The Content-Type header is application/problem+json. On field-level validation errors a non-empty errors[] array also appears, each entry carrying a docs_url to its error code's page.