Resilience · Difficulty 2 of 5 · 15 min
Poison records vanish after retries
Records are consumed, but malformed ones vanish after repeated failures and are never seen again. A similarly named function with different time limits also exists. Keep failed records for replay instead of losing them.
Where the symptom shows: Kinesis
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
- ResilienceFailed background requests vanishLambda · 15 min · level 2
- ResilienceBad messages with nowhere to goSQS · 25 min · level 3
- ResilienceFailed deliveries leave no traceEventBridge · 10 min · level 1
- ResilienceThe same order is processed twiceLambda · 5 min · level 1
- ResiliencePrivate workloads reach nothing they depend onEC2 · 90 min · level 5
- AccessWorkflow that stops at step oneStep Functions · 15 min · level 2