Observability · Difficulty 1 of 5 · 5 min
Failed runs leave no history
Failed workflow runs cannot be diagnosed because they leave no history anywhere. A log destination with a name like the workflow's exists. Make failures diagnosable again.
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
- ObservabilityAssistant activity is no longer recordedBedrock AgentCore · 10 min · level 1
- ObservabilityModel usage leaves no recordAmazon Bedrock · 10 min · level 1
- ObservabilityThe activity record went quietCloudTrail · 5 min · level 1
- ObservabilityAlarm fires, nobody gets pagedCloudWatch · 10 min · level 1
- ObservabilityNo trace of public API trafficAPI Gateway · 15 min · level 2
- ObservabilityAn error spike no alarm noticedLambda · 20 min · level 3