batch-unavailable

batch-unavailable

HTTP 503 Service Unavailable
Content-Type: application/problem+json

{
  "type": "https://docs.transmute.403fin.io/errors/batch-unavailable",
  "title": "...",
  "status": 503,
  "detail": "...",
  "requestId": "req_01J..."
}

The batch/jobs/connections subsystem is not available on this deployment (its encrypted job storage is not configured). The synchronous API is unaffected.

Common causes

• On-prem/self-hosted deployments without a job encryption key configured

How to fix it

Self-hosting: configure the job encryption key (see your deployment runbook). On the hosted API this should not occur — contact support with the X-Request-Id.

Does it bill?

No. See Test vs Live Keys for the full billing rules.

Related

• Errors Overview — the problem+json shape and the closed catalog
• Every response carries an X-Request-Id; quote it when contacting support.