Observability · Difficulty 3 of 5 · 20 min
Every run fails and nothing explains why
Workflow runs fail immediately, pointing at a piece of work that no longer exists, and no run history appears anywhere. A second log destination with a similar name exists. Restore a working workflow and a full, observable history.
Where the symptom shows: Step Functions
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
- ObservabilityAn error spike no alarm noticedLambda · 20 min · level 3
- ObservabilityLog storage costs keep climbingAWS Config · 15 min · level 3
- ObservabilityTwo incidents that alerted nobodyLambda · 20 min · level 3
- ObservabilityNo trace of public API trafficAPI Gateway · 15 min · level 2
- ObservabilityAssistant activity is no longer recordedBedrock AgentCore · 10 min · level 1
- ObservabilityModel usage leaves no recordAmazon Bedrock · 10 min · level 1