Event delivery · Difficulty 1 of 5 · 5 min
Orders stop mid-pipeline
Orders pile up at the start of the pipeline and never reach the next stage, although the forwarding function keeps running on them. A second output queue with no consumer exists. Find where the orders stop and get them moving.
Where the symptom shows: SQS
Take this challenge on a live account
A live AWS account, already broken, and a clock. You fix it with the provider's own console and command line, then read a report of how you worked. We host the cloud account. Nothing lands on your bill.
More challenges
- Event deliveryMidnight batch jobs stop firingLambda · 5 min · level 1
- Event deliveryEvery incoming message fails to parseLambda · 5 min · level 1
- Event deliveryEvents that vanish on successEventBridge · 15 min · level 2
- Event deliveryDocuments arrive but no run ever startsStep Functions · 15 min · level 2
- Event deliveryRequests logged, bookings never followStep Functions · 5 min · level 2
- Event deliveryThe request reader has gone quietSQS · 5 min · level 2