Jobs stuck in a RUNNABLE status

Suppose that your compute environment contains compute resources, but your jobs don't progress beyond the RUNNABLE status. Then, it's likely that something is preventing the jobs from being placed on a compute resource and causing your job queues to be blocked. Here's how to know if your job is waiting for its turn or stuck and blocking the queue.

If AWS Batch detects that you have a RUNNABLE job at the head and blocking the queue, you'll receive a Job queue blocked events event from Amazon CloudWatch Events with the reason. The same reason is also updated into the statusReason field as a part of ListJobs and DescribeJobs API calls.

Specific reasons are inferred by AWS Batch based on the state of connected compute environments and fall into three categories: capacity issues, misconfiguration, and invalid compute environments. Optionally, you can configure the jobStateTimeLimitActions parameter on your job queue to automatically cancel jobs that remain stuck in RUNNABLE for longer than a specified threshold. If none of the specific reasons in the following sections match your situation, or if your statusReason shows UNDETERMINED, see Jobs stuck in RUNNABLE with undetermined root cause and Common causes of jobs stuck in RUNNABLE without a statusReason for manual troubleshooting steps.