execution took longer than 1h0m0s CI/CD Origin: Build & delivery Last updated 25 Oct 2026

GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds

The job ran past its timeout (project default is 60 minutes) and GitLab killed it.

Exact message you may see ERROR: Job failed: execution took longer than 1h0m0s secondsexecution took longer thanJob failed: execution took longer than 1h0m0s secondsjob timed out GitLab
Explore the map of this error Full error map →
Seen on: GitLab CI

Meaning

Hung processes and interactive prompts are the usual cause. Set a realistic timeout: on slow jobs, make commands non-interactive, and find the step that stalls using timestamps in the log. Runners can also impose a maximum job timeout that overrides the project setting.

Common causes

  • Command waiting for input or a lock
  • Network call without timeout
  • Tests deadlocked or very slow on a small runner
  • Service container never healthy
  • Project/runner timeout set lower than the job needs

⚡ Quick fix

  1. Add timeout: 30m per job to fail fast, or raise it for long builds
  2. Run steps non-interactively and with explicit timeouts
  3. Check the runner's maximum job timeout

Detailed fix by platform

GitLab CI

  1. Settings → CI/CD → General pipelines → Timeout
  2. Use script: - timeout 20m ./long-task.sh

Code examples

Per-job timeout

yaml
integration:
  timeout: 30m
  script:
    - timeout 25m ./run-integration.sh

How to diagnose

  1. Last output — Where did the log stop?
  2. Prompt — Waiting for input?
  3. Limits — Job vs runner timeout?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):

Cannot connect to the Docker daemon (GitLab) — GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running? (CI/CD)Cannot connect to the…exceeded the maximum execution time — GitHub Actions: The job running on runner GitHub Actions 12 has exceeded the maximum execution time of 360 minutes (CI/CD)exceeded the maximum …failed to pull image (GitLab) — GitLab CI: ERROR: Job failed: failed to pull image "registry.example.com/app:latest" with specified policies [always]: access forbidden (CI/CD)failed to pull image …Job depends on artifacts that have expired — GitLab CI: This job could not start because it could not retrieve the needed artifacts (dependencies: build). (CI/CD)Job depends on artifa…This job is stuck because you don't have any active runners — GitLab CI: This job is stuck because you don't have any active runners online or available with any of these tags assigned to them (CI/CD)This job is stuck bec…Too long with no output — CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded (CI/CD)Too long with no outp…Uploading artifacts: too large archive — GitLab CI: ERROR: Uploading artifacts as "archive" to coordinator... too large archive id=123 responseStatus=413 Request Entity Too Large (CI/CD)Uploading artifacts: …execution…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.