recourse_unavailable: Terms cases are not available here
A terms breach case resolves through the stream's breach refund, which needs the verified runtime (CORE_VERIFIED=1) for the stream's funding mode on this deployment. Without it, opening such a case is refused and nothing is opened; resolving one is refused and nothing changes.
A deployment that runs the verified runtime but whose stream carries no accepted catalogue terms (for example, no terms catalogue is configured) answers recourse_claim_invalid instead.
What to do
- Terms breach cases need the verified runtime (
CORE_VERIFIED=1) on this deployment; the stream must also carry accepted catalogue terms.
On the wire
HTTP 409, error type state_error. Without Dynamo-Error-Detail: 1 every client receives {"error": "state", "reason": "recourse_unavailable", "detail": "…"} with no errorDetail: the owner and payee recourse routes add it only when the request sends that header, on a single-tenant core and on the hosted tier alike.
With Dynamo-Error-Detail: 1:
{
"error": "state",
"reason": "recourse_unavailable",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "recourse_unavailable",
"message": "…",
"param": "case",
"doc_url": "…/errors/recourse_unavailable.md",
"fix": "terms breach cases need the verified runtime with a terms catalogue on this deployment"
}
}
See recourse and all error codes.