Event delivery · Difficulty 1 of 5 · 5 min
Midnight batch jobs stop firing
Batch jobs stopped running at midnight: the batch system still emits an event for each job, but the downstream function no longer runs. The routing and its target look configured, and a similarly named log group hints at a logging fault. Restore reliable automatic execution.
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 deliveryEvery incoming message fails to parseLambda · 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