Ordering-break acknowledgement is required to discard

https://tandem.codingful.com/problems/ordering-break-not-acknowledged

What it means

A discard was requested without acknowledgeOrderingBreak: true in the body.

Discarding abandons an event permanently so the relay stops blocking its aggregate. That unblocks delivery, but it also means the events after it are published without the one you skipped — the per-aggregate happens-before guarantee, the core promise of the library, is broken for that aggregate from then on. Consumers that rely on it may already have processed a prefix that no longer leads to the state they are about to see.

What to do

Decide whether that is acceptable for this aggregate. If it is, repeat the request with the flag set and a reason — both are recorded in the audit log alongside the caller's identity when the host application authenticates requests.

If it is not acceptable, the alternative is to fix the cause of the failure and replay instead: a message that keeps failing usually points at a broken payload, an unreachable broker, or a topic that does not exist.

Example

{
  "type": "https://tandem.codingful.com/problems/ordering-break-not-acknowledged",
  "title": "Ordering-break acknowledgement is required to discard",
  "status": 400
}