Skip to content
deedglassdocs

witness_not_configured

GET or DELETE /v1/connectors/{id}/decoder named a connector that isn’t witnessed: it isn’t a postgres connector, or its config has witness.enabled: false, so there is no slot and no decoder to show…

HTTP 409 · invalid_request_error · not retryable

What happened

Section titled “What happened”

GET or DELETE /v1/connectors/{id}/decoder named a connector that isn’t witnessed: it isn’t a postgres connector, or its config has witness.enabled: false, so there is no slot and no decoder to show or drop.

What to do

Section titled “What to do”

Set witness.enabled: true (and witness.watched_tables) in the connector’s config, run deedglass connector postgres init and deedglass connector postgres check, then look again with deedglass decoder status --connector <name>.

Example

Section titled “Example”
HTTP 409 · witness_not_configured
{
  "error": {
    "type": "invalid_request_error",
    "code": "witness_not_configured",
    "message": "Checks aren't on for this connector, so it has no decoder. Turn on witness.enabled in its config first.",
    "param": null,
    "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d",
    "doc_url": "https://docs.deedglass.com/errors/witness_not_configured"
  }
}

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) InvalidRequestError with code === "witness_not_configured"
Python (deedglass) deedglass.InvalidRequestError with .code == "witness_not_configured"
Section titled “Related”