Event delivery · Difficulty 1 of 5 · 5 min
Every incoming message fails to parse
Downstream consumers log a parse failure on every message, though publishing upstream keeps succeeding. Another delivery path produces messages that look well formed. Make what arrives match what the consumer expects to read.
Where the symptom shows: Lambda
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 deliveryOrders stop mid-pipelineSQS · 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