bug: StepFunctions: SecondsPath in Wait state throws error #10505
Labels
aws:stepfunctions
AWS Step Functions
status: backlog
Triaged but not yet being worked on
type: bug
Bug report
Is there an existing issue for this?
Current Behavior
Using a
SecondsPath
with aWait
state in a step function definition makes the execution fail with the following error in the logs even though a valid input is provided:The same step function definition and input work in AWS.
Expected Behavior
The
Wait
state should take the value from the location specified inSecondsPath
and wait for that duration as described in the AWS docsHow are you starting LocalStack?
With a docker-compose file
Steps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Create a state machine using either awslocal or the localstack resource browser with the following ASL definition:
Start an execution of the state machine using either awslocal or the localstack resource browser with the following input:
The execution fails immediately in LocalStack whereas in AWS the execution proceeds and waits for 60 seconds as expected before completing.
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: