Poison message blocks order queue
An order-state worker consumes an SQS FIFO queue, partitioned by `MessageGroupId = order_id` so each order's events process in order. At 10:15 a subset of orders stop advancing — their later events never process — while most orders are fine. Dashboards: `ApproximateNumberOfMessagesVisible` is flat-ish, but a few message groups show messages stuck and the worker logs an unhandled exception on one message that keeps reappearing after the visibility timeout. No DLQ is configured. How do you triage, unblock the stuck orders, and harden the consumer?
What a strong answer looks like
Stop the bleeding first (mitigate), then form hypotheses from real signals. Separate root cause from symptom, communicate status as you go, and close with what prevents a repeat.
0:00 of about 35 min
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.