breach_unmatched: No accepted breach report
A terms refund needs the stream's recorded break point to come from an accepted breach report. Nothing moves.
In practice this happens when the stream's break point was already recorded by the objective-SLA oracle (on a deployment that runs verified settlement) rather than by a breach report. A breach report at the same instant is then stored, but the refund refuses with this code. A recourse case of kind terms_breach on such a stream meets the same code when it is resolved (POST /owner/v1/recourse/cases/{id}/resolve).
What to do
- If the SLA oracle recorded the stream's break point, the terms refund path does not apply to that stream; its refund follows verified settlement instead.
On the wire
HTTP 409, error type state_error.
The breach report routes answer this code: POST /owner/v1/streams/{id}/breach-reports (1.7.0) and, where the deployment serves it, the oracle's POST /oracle/v1/attest/breach (1.8.0). Both send errorDetail to every client, with or without Dynamo-Error-Detail: 1, as below. The recourse resolve route adds errorDetail only when the request sends Dynamo-Error-Detail: 1.
{
"error": "state",
"reason": "breach_unmatched",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "breach_unmatched",
"message": "…",
"param": "report",
"doc_url": "…/errors/breach_unmatched.md",
"fix": "no accepted breach report matches this stream; nothing moved"
}
}
See all error codes.