Call StepFunction SendTaskSuccess once then got: Task Timed Out: 'Provided task does not exist anymore', but succeeded eventually #4044
Labels
bug
This issue is a confirmed bug.
closed-for-staleness
p2
This is a standard priority issue
response-requested
Waiting on additional information or feedback.
service-api
This issue is caused by the service API, not the SDK implementation.
stepfunctions
Describe the bug
I have code that consumes messages from SQS stand queue, each message will make a call to StepFunction SendTaskSuccess. I checked log that one message only called StepFunction SendTaskSuccess once with valid
task token
and got:I also saved the message id in DynamoDB, it was the same message that updated the DB item which caused
TaskTimedOut
Looks like boto3 had made the first attempt to send StepFunction task token and the token expired, but
eventually
the SendTaskSuccess operation succeeded even with exception like above, and StepFunction successfully received thetask token
.Any boto3 inside retry mechanism leads to this issue?
Expected Behavior
Should be no exception:
when making first call
Current Behavior
Got exception
even with first call to SendTaskSuccess, but eventually the SendTaskSuccess operation succeeded.
Reproduction Steps
The error was random, I tried to send about greater than 10K requests then there was one
TaskTimedOut
exception.Possible Solution
No response
Additional Information/Context
No response
SDK version used
Boto3==1.34.50, BotoCore==1.34.50
Environment details (OS name and version, etc.)
AWS Lambda Python 3.9 x86_64
The text was updated successfully, but these errors were encountered: