How a Business ID Fixed Log Correlation Across AWS Step Functions Lambdas

A software engineer with over 15 years of experience describes a recurring debugging problem caused by inconsistent logging across multiple AWS Lambda functions in a Step Functions pipeline. Without a shared identifier in logs, reconstructing the sequence of events for a specific execution required manually piecing together log groups from each Lambda in order. The root cause was that each function logged independently, with no common field linking them, and AWS Step Functions execution history only persists for 90 days. The engineer's solution was to reuse the existing business case ID as a correlationId across all Lambda logs, avoiding the need for a separate generated identifier. The fix relied on a field already available within Step Functions, requiring no new infrastructure — only consistent structured logging across the pipeline.