How to fix Job not running in Kubernetes

KubernetesINTERMEDIATEMEDIUMUpdated Dec 7, 2025· 103 views

This error indicates that a job is in a suspended or failed state and is not executing. This typically happens when the job is explicitly suspended, has exceeded retry limits, or has persistent pod failures.

Quick fix

Fixes Job not running

  1. Check job status
  2. Check if suspended
  3. Check pod logs
  4. Verify image
  5. Increase backoffLimit
kubernetes — error
# Job not running
Job not running

What this error means

The "Job not running" error means that a Job exists in your cluster but is not actively executing pods. Jobs can be in several non-running states: Suspended (paused), Failed (exceeded backoffLimit), or Completed (finished).

Typical symptoms

  • Job shows 0 active pods
  • kubectl describe job shows Suspended
  • Job completions stuck
  • Job age increasing but pods don't run

Common causes

  1. Job suspended by policy
  2. Job exceeded backoffLimit
  3. Pod image doesn't exist
  4. Pod container crashes immediately
  5. Resource quotas preventing pod creation

How to fix "Job not running"

1Check job status

kubectl describe job <job-name>

2Check if suspended

kubectl get job <name> -o jsonpath='{.spec.suspend}'

3Check pod logs

kubectl logs <pod-name>

4Verify image

kubectl get job <name> -o yaml | grep -A5 containers

5Increase backoffLimit

kubectl patch job <name> -p '{"spec":{"backoffLimit":10}}'

Advanced notes

The backoffLimit default is 6. After 6 failed attempts, the job marks as Failed.

Frequently asked questions

What does "Job not running" mean?
The "Job not running" error means that a Job exists in your cluster but is not actively executing pods. Jobs can be in several non-running states: Suspended (paused), Failed (exceeded backoffLimit), or Completed (finished).
How do I fix "Job not running"?
This error indicates that a job is in a suspended or failed state and is not executing. This typically happens when the job is explicitly suspended, has exceeded retry limits, or has persistent pod failures.
What causes "Job not running"?
Job suspended by policy Job exceeded backoffLimit Pod image doesn't exist
Is the "Job not running" error serious?
It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Official resources & further reading