CI Step Timed Out (timeout-minutes Exceeded)

By Daniel Zoghalchali·Latchkey

A step ran past its timeout-minutes and was cancelled. This guards against hangs, but a transient slowdown (slow fetch, not-yet-ready service) can also trip it on otherwise healthy work.

What this error means

A step ends with a cancellation noting the timeout was reached. If a transient slowdown caused it, a re-run completes; a true hang reproduces every time.

##[error] The action 'Run tests' has timed out after 15 minutes.

Common causes

A transient slowdown exceeded the limit

A slow download or a service that took longer than usual to respond pushed the step past its timeout.

The step actually hangs

A deadlock, interactive prompt, or waiting on something that never arrives runs until the timeout fires.

How to fix it

Diagnose hang vs slow

1. Add verbose logging to see where the step stalls.
2. Ensure no command waits on interactive input (use non-interactive flags).
3. Add an internal timeout to the slow command so it fails fast with context.

Speed up or raise the limit

Cache to cut runtime, or bump the timeout if the work is legitimately longer.

timeout 600 ./long-task.sh   # fail fast with context
# or raise timeout-minutes in the step

How to prevent it

• Set timeout-minutes to a realistic ceiling per step.
• Make commands non-interactive in CI.
• For a transient infra slowdown, managed runners detect the mechanical blip and automatically retry, so a one-off slow step does not fail the build.

Frequently asked questions

Related guides

References

• GitHub Actions documentation