Too long with no output CI/CD Origin: Build & delivery Last updated 25 Oct 2026

CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded

A CircleCI step printed nothing for 10 minutes, so CircleCI assumed it hung and cancelled it.

Exact message you may see Too long with no output (exceeded 10m0s): context deadline exceededToo long with no outputexceeded 10m0s context deadline exceeded CircleCI
Explore the map of this error Full error map →
Seen on: CircleCI

Meaning

The default no_output_timeout is 10 minutes. Long silent commands (big test suites, deployments, builds) need either periodic output or a larger no_output_timeout. If the step is truly stuck, fix the hang rather than raising the limit.

Common causes

  • Long-running command with no logs
  • Hung process waiting for input or a lock
  • Slow network step (download, deploy)
  • Tests running in silent mode
  • Resource class too small, so the step crawls

⚡ Quick fix

  1. Set no_output_timeout: 30m on the step
  2. Print progress (verbose flag, while sleep 60; do echo .; done &)
  3. Use a larger resource class or split the work

Detailed fix by platform

CircleCI

  1. Add to the step: no_output_timeout: 30m

Code examples

Longer silent timeout

yaml
- run:
    name: Integration tests
    command: ./run-integration.sh
    no_output_timeout: 30m

How to diagnose

  1. Silence — What step produced no output?
  2. Hang — Genuinely stuck?
  3. Resources — Resource class sufficient?

🔧 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 find orb — CircleCI: Cannot find orb 'circleci/node@9.9.9'. Check the namespace and version exist (CI/CD)Cannot find orbComparisonError: manifest generation failed — Argo CD: ComparisonError: rpc error: code = Unknown desc = Manifest generation error (cached): kustomize build failed (CI/CD)ComparisonError: mani…Config compilation failed — CircleCI: Error calling workflow: 'build'. Cannot find a definition for job named test / Config does not conform to schema (CI/CD)Config compilation fa…Container exceeded memory limit — Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137 (CI/CD)Container exceeded me…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 …execution took longer than 1h0m0s — GitLab CI: ERROR: Job failed: execution took longer than 1h0m0s seconds (CI/CD)execution took longer…Template file not found — Azure Pipelines: /azure-pipelines.yml: File /templates/build.yml not found in repository / Unable to find template (CI/CD)Template file not fou…Too long …

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.