1 Answer
- Newest
- Most votes
- Most comments
0
If the workflow is failing with "Max concurrent runs exceeded" error message even though the job is not running, it could be an issue with workflow not being able to keep track of concurrent job runs of the job. Please reach out to AWS Support with workflow name and failed workflow run id so that we can take a look at your workflow and assist you with this.
Relevant content
- asked 2 years ago
- asked 3 months ago
- asked 9 months ago
- Accepted Answerasked 5 years ago
- How can I use a Lambda function to automatically start an AWS Glue job when a crawler run completes?AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago