search

aws-solutions / content-analysis-on-aws

As of August 30, 2023, this AWS Solution is no longer available. Existing deployments will continue to run. The functionality provided by Content Analysis on AWS will be superseded with functionality in Media2Cloud on AWS and Content Localization on AWS. We encourage you to explore these solutions.
https://aws.amazon.com/solutions/implementations/aws-content-analysis/
Apache License 2.0
96 stars 47 forks source link

Failed workflows block other workflows from running #3

Closed ianwow closed 1 year ago

ianwow commented 4 years ago

Failed workflows can get stuck in a "Started" state. This causes the concurrent execution queue to fill up with failed workflows that look like they're "Started" but are actually failed. You can see their real status if you look at their state machine in AWS Step Functions.

To clear the concurrent execution queue, open the content-analysisWorkflowExecution table in DynamoDB and remove one or more of the records for assets which are stuck in a Started status, like this:

imageimage

markotitel commented 4 years ago

@ianwow could you add s screenshot of StepFunctions, so that I could get a better view which will help me to quickly get to the code pieces. I am interested in working on this issue.

ianwow commented 4 years ago

@ianwow could you add s screenshot of StepFunctions, so that I could get a better view which will help me to quickly get to the code pieces. I am interested in working on this issue.

There are some screenshots of StepFunctions here: https://docs.aws.amazon.com/solutions/latest/aws-content-analysis/appendix-c-state-machines.html

Thanks for checking out this issue!

markotitel commented 4 years ago

@ianwow I have deployed the solution and am aware of stepfunctions. Could you screenshot where it broke for you?