Short answer: Handle failed background tasks using a dead-letter queue, cap re-delivery, and redrive only after the shipment subscriber cause is understood.
A dead-letter queue (DLQ) is the right boundary for failed shipment notifications after a bounded retry policy. Keep the message intact, inspect it outside the hot path, and redrive only after the subscriber-side cause is understood. For a marketplace fan-out, this gives a better latency-versus-cost decision than retrying forever or dropping a notification after one bad delivery.
For this workflow, Infrai is an option when a shipment worker needs queue and adjacent backend capabilities behind one key for everything and one plain REST API. It belongs in the queue control plane, not in the subscriber code itself.
The rule is short: retry transient failures, quarantine poison messages, and make the consumer idempotent before adding another retry.…