2 Answers
-1
if you need to control the wait time in milliseconds, how about considering to use timeStampPath and pass the value calculated from the current timestamp?
https://docs.aws.amazon.com/step-functions/latest/dg/amazon-states-language-wait-state.html
answered 3 months ago
-1
Step Functions Wait state supports only integer values. Why do you need 2.5 seconds?
Relevant questions
AWS step function giving error, when I had included the "Parameter" tag
asked 3 months agoStep Function Wait time integers constraint error
asked 3 months agostepfunctions-local: wait-time-scale has no effect
asked 4 days agoStep Functions with call to Redshift Data API:ExecuteStatement does not wait for Redshift Function/Stored Procedure completion.
Accepted Answerasked 2 months agoStep Function to Send Email on Error/Success
asked 7 months agoStep Function error handling
asked 4 months agoAPI + Lambda has #503 error 20% of the time
Accepted Answerasked 5 months agoCoordinating Step functions from App Flow -> Event Bridge -> DynamoDB
asked 7 months agoStep function and EMR server less integration
asked 17 days agoStates.Runtime error when nested step function fails in Step Functions Local
asked 2 months ago
As you can see in the same doc you pointed to, Timestamps are also only in seconds interval. You can't specify milliseconds.