Skip to content
deedglassdocs

vault_unavailable

Deedglass couldn’t open a connector’s credential: it is wrapped by a key that isn’t in DEEDGLASSVAULTKEY, or it failed to authenticate (a row moved to another org or connector, or changed on disk…

HTTP 503 · api_error · safe to retry

What happened

Section titled “What happened”

Deedglass couldn’t open a connector’s credential: it is wrapped by a key that isn’t in DEEDGLASS_VAULT_KEY, or it failed to authenticate (a row moved to another org or connector, or changed on disk; the server logs the vault_integrity alert). Nothing was sent: the action is failed with this error code. Agents see only that an admin was alerted.

What to do

Section titled “What to do”

If a key was removed too early, add it back as the second key, restart, and run deedglass vault rotate (VAULT.md). If the row failed to authenticate, store the credential again.

Example

Section titled “Example”
HTTP 503 · vault_unavailable
{
  "error": {
    "type": "api_error",
    "code": "vault_unavailable",
    "message": "Deedglass couldn't open this connector's credentials. An admin has been alerted.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/vault_unavailable"
  }
}

The message is for a person and can get more exact over time: branch on type and code, never on the message.

In the SDKs

Section titled “In the SDKs”
SDK Raised as
TypeScript (@deedglass/sdk) APIError with code === "vault_unavailable"
Python (deedglass) deedglass.APIError with .code == "vault_unavailable"
Section titled “Related”