breach_conflict: Another breach time is already recorded
The first accepted report fixes the stream's breach time; a later report must repeat it. Nothing moves.
What to do
- Send reports that repeat the recorded breach time.
On the wire
HTTP 409, error type state_error.
Only 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:
{
"error": "state",
"reason": "breach_conflict",
"detail": "…",
"errorDetail": {
"type": "state_error",
"code": "breach_conflict",
"message": "…",
"param": "report",
"doc_url": "…/errors/breach_conflict.md",
"fix": "a different break-point is already recorded for this stream; the first accepted report stands"
}
}
See all error codes.