Stop the mail without losing it verifiedimportantWritten by the Hub
Held mail waits rather than fails — as long as the target is named and the removal matches the fields that created it.
In detail
Two mistakes, both measured. A body the engine does not understand — a form-encoded one, a misspelled field — creates a cluster-wide pause with no expiry and answers 200 with {"cluster": true}. And expire is an absolute timestamp: passing a duration in seconds creates a pause that expired decades ago and does nothing at all. Removal is by field match, not by id. {"id": 4} returned 200 and left the pause in place; {"domain": …, "cluster": false} removed it. The console's own endpoint does delete by id, which is the faster road when a pause has to go now.