CircleCI "Too long with no output (exceeded 10m0s)" timeout

CircleCI kills a step that emits no output for the no_output_timeout window (10 minutes by default). The step may still be working, but a silent long-running command looks hung.

What this error means

The step ends with "Too long with no output (exceeded 10m0s): context deadline exceeded" even though the command was progressing.

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

Common causes

A long silent command

A build, download, or test that buffers output produces nothing for over 10 minutes, so CircleCI assumes it hung.

A command waiting on input or a stuck network call

A process blocked on stdin or a hanging connection emits no output and trips the timeout.

How to fix it

Raise no_output_timeout for the step

1. Identify the legitimately slow step.
2. Set no_output_timeout to a value above its real duration.
3. Re-run to confirm it completes.

steps:
  - run:
      command: ./long-build.sh
      no_output_timeout: 30m

Emit periodic progress

Make the command print progress (unbuffered) so it never looks silent.

- run: stdbuf -oL ./long-build.sh | tee build.log

How to prevent it

• Set realistic no_output_timeout on known-slow steps.
• Stream progress output for long commands.
• Cache dependencies so silent download phases shrink.

Related guides