AWS Step Functions execution scenarios with 'InvalidExecutionInput' despite valid input format
I'm refactoring my project and I've spent hours debugging this and I'm currently working on an AWS Step Functions workflow that orchestrates a series of Lambda functions. The workflow is designed to process user data, but I keep receiving an 'InvalidExecutionInput' behavior when I start the execution, even though my input seems valid. I've double-checked my state machine definition and the input format. Here's the relevant part of my state machine definition: ```json { "Comment": "A Hello World example of the Amazon States Language", "StartAt": "ProcessUserData", "States": { "ProcessUserData": { "Type": "Task", "Resource": "arn:aws:lambda:us-east-1:123456789012:function:ProcessUserData", "End": true } } } ``` I start the execution with the following input: ```json { "userId": "12345", "userData": { "name": "John Doe", "email": "john.doe@example.com" } } ``` I confirmed that the Lambda function accepts the input format, and I also tried using a simpler input to isolate the scenario, but I still get the same behavior. I validated the JSON structure, and it looks correct. The execution role for the Step Functions seems to have the necessary permissions, as it can invoke the Lambda function directly. I even checked the AWS CloudWatch logs, but there are no additional behavior details for the Step Functions execution, just the invalid input behavior code. Is there something I'm missing in the configuration of the Step Functions or the Lambda function? Any pointers would be greatly appreciated! Thanks in advance! This is for a REST API running on Debian. What's the best practice here? Could this be a known issue?