Step Function: stuck delete status, case created 12 days ago

0

I created an AWS support case about 10 days ago. It was kind of simple in nature. I had a Step Function which was in delete phase for almost a month. I double checked in the Management Console, and verified there was no running/pending/stuck tasks. Yet it was in "Delete" status. I created a support ticket stating that I would like the Step Function deleted. I got a response from a support engineer, who corrected me and said the Step Function has been in delete status for 19 days. That's pretty good Star Principle, and very accurate, much appreciated. However, the case has been open since February 8th. It's now February 20th, and the Step Function has now been in delete status for 31 days. Is this part of AWS star principle processes?

asked 2 months ago319 views
3 Answers
0

Just for anyone self-awareness. Prior to creating the case, I went to the step function that was pending deletion for 19 days, and selected from the drop down on the Management Console "Filtered by status" with the value "Running". It returned no results, and that is when I proceeded to the create the AWS case. When the case was first opened I was asked to the run the AWS CLI variation of what I did in the console, in which I responded in case:

>(yes-please) jeff1evesque@computer pooPoo % aws stepfunctions list-executions --state-machine-arn arn:aws:states:us-beast-7:xxxxxxxxxxxx:stateMachine:NotHotDog --status-filter RUNNING
{
    "executions": []
}

Sometime later, I was told there were executions discovered via AWS internal tools indicating some executions that were not stopped (not sure that means it's "Running"), which prevented the step function from deletion. That being said, I had to manually delete the executions:

>(yes-please) jeff1evesque@computer pooPoo % aws stepfunctions stop-execution --execution-arn << EXECUTION ARN>>

If that helps anyone, great. If not, contact your support to find out what executions are running, but not appear "Running".

answered 2 months ago
0

You are correct, In order to see all the currently running executions, you'll need to use the AWS CLI. You can do this by running below CLI command

==> aws stepfunctions list-executions --state-machine-arn << STATE_MACHINE_ARN >> --status-filter RUNNING

[+] https://docs.aws.amazon.com/cli/latest/reference/stepfunctions/list-executions.html

Based on the output of the above CLI command if there are any running executions then you have to stop them by running the below CLI command

==> aws stepfunctions stop-execution --execution-arn << EXECUTION ARN>>

[+] https://docs.aws.amazon.com/cli/latest/reference/stepfunctions/stop-execution.html

After all the executions are stopped you can finish deleting again.

[+] https://docs.aws.amazon.com/cli/latest/reference/stepfunctions/delete-state-machine.html

However, In an exceptional scenario, should there be no RUNNING executions yet difficulties persist in deleting the state machine, it is advisable to reach out to AWS support for assistance in identifying the underlying issue.

AWS
answered 2 months ago
profile picture
EXPERT
reviewed a month ago
0

Ran into the same problem again. Delete Step functions, ran the CLI and no running tasks, yet the step functions have been in deleting state for 30 minutes. If you don't have paid AWS support, I'm not sure how to reconcile these problems. Will have to open another paid support case.

answered 8 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions