recourse_claim_invalid: The case names no objective fact
A recourse case names exactly one objective fact: a breach report signed by a catalogue signer the payer opted into that shows a breach of the stream's terms, a Task Allowance milestone of the stream, or a payment record of the stream. Anything else is refused: a terms case on a stream with no accepted catalogue terms, a report that does not show a breach or that the breach intake does not admit, a milestone or payment record that is not this stream's. Nothing was opened. A claim of another shape answers 400 invalid_request first.
Resolving a case answers the same code when the task milestone or payment record it names is no longer there; nothing changed.
What to do
- A case names one objective fact: a breach report that shows a breach of the stream's catalogue terms, a task milestone of the stream, or a payment record of the stream; nothing was opened.
On the wire
HTTP 409, error type state_error. Without Dynamo-Error-Detail: 1 every client receives {"error": "state", "reason": "recourse_claim_invalid", "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_claim_invalid",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "recourse_claim_invalid",
"message": "…",
"param": "case",
"doc_url": "…/errors/recourse_claim_invalid.md",
"fix": "a case names one objective fact: a breach report that shows a breach of the stream's catalogue terms, a task milestone of the stream, or a payment record of the stream; nothing was opened"
}
}
See recourse and all error codes.