Dead-letter queues
Seven queues across the two gateway services. Counts refresh on page load.
Warning
A dead-letter on any of the publisher queues is a TRACES update dropped on the way to BTMS or MDM, with no compensating path. Those are the ones to watch.
| Queue | Service | Messages | Oldest (UTC) | Action |
|---|---|---|---|---|
trade_gateway_ched_attachments_internal_downloader-deadletter |
trade-gateway | 0 | — | — |
trade_gateway_publisher_ched-deadletter |
trade-gateway-publisher | 12 | 18 Nov, 06:04 | Redrive |
trade_gateway_publisher_ched_asb_publisher-deadletter |
trade-gateway-publisher | 0 | — | — |
trade_gateway_publisher_intra-deadletter |
trade-gateway-publisher | 3 | 18 Nov, 08:12 | Redrive |
trade_gateway_publisher_intra_asb_publisher-deadletter |
trade-gateway-publisher | 0 | — | — |
trade_gateway_publisher_refdata-deadletter |
trade-gateway-publisher | 0 | — | — |
trade_gateway_publisher_refdata_asb_publisher-deadletter |
trade-gateway-publisher | 0 | — | — |
Data source: GetCount per queue, via MapDeadLetterQueueEndpoints in Defra.Trade.Imports.SQS.Endpoints — the same shared package btms-gateway wires in one call. Neither gateway service maps an admin route on origin/main today, so this is a wiring job, not new code.
Before you redrive
- The attachment-download queue has its own recovery: ChedAttachmentService re-publishes records stuck past RetryAfter, so that dead-letter is a shortcut rather than the only path.
- Redrive is not a fix for a broken consumer. Check the consumer's health first, or the messages will come straight back.
- Local stacks use maxReceiveCount 1 where the tenant says 3, so dead-lettering behaves differently on a dev stack.
A consumer without the support admin group does not see this section at all — they get You do not have access to this page instead.
Queue depth, age and DLQ greater than zero are already per-service Grafana dashboards and alerts on CDP. This page exists for the action, not for the chart.