An AWS Step Functions Standard workflow that loads a data warehouse failed overnight. Nobody configured CloudWatch Logs logging on the state machine. The on-call engineer must find which state failed, the input that state received, and the error and cause it returned. Where can the engineer find all three?
Choose one.
Step Functions Standard workflows record an event history for every execution: each state entered and exited with its input and output, and the error and cause of any failure.
The execution event history is built into Standard workflows. The console graph highlights the failed state, and its events show the input, the error name and the cause; GetExecutionHistory returns the same data to scripts. CloudWatch Logs logging is an optional extra (and the main source for Express workflows), so it is absent here. CloudTrail covers API calls on the state machine rather than its internal steps, and CloudWatch metrics are counts.
- Open the state machine and select the failed execution.
- Use the graph view to find the state marked as failed.
- Read that state's events for its input, error name and cause.
- Use GetExecutionHistory when the same detail is needed by automation.
Exam tip: For a failed Standard workflow, the execution event history answers which state failed, with what input and what error.
Automate Data Processing on AWS: Step Functions, MWAA, Lambda & EventBridge — the lesson that teaches this.