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

**Code:** `Too long with no output` · **Category:** CI/CD · **Seen on:** CircleCI

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

## 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?

---
Source: [WhatIsMyError](https://whatismyerror.com/errors/cicd/circleci-no-output-timeout)