Job timeouts and cancellations — exceeded the maximum execution time

Log signatures

has exceeded the maximum execution time of 360 minutes
The operation was canceled
Too long with no output
ERROR: Job failed: execution took longer than
ran longer than the maximum time of 60 minutes

What’s happening

Three distinct causes share these signatures, and telling them apart matters: a real time limit ("exceeded the maximum execution time") — the job is genuinely too slow, or it hung; matrix fail-fast cancellation ("The operation was canceled" on a job that was passing) — a sibling matrix job failed and CI killed the rest, so your job was innocent; output stall ("Too long with no output") — the process is alive but silent, usually a hung subprocess or a prompt waiting for input that will never come.

Fix playbook

1. 1Check whether this job failed or was canceled because a sibling failed. If sibling: triage the sibling, ignore this log.
2. 2If it's a real timeout, compare this run's step durations against the last green run. A step that went from 4 to 40 minutes is a hang, not slowness — look for an interactive prompt, a deadlock, or an unbounded retry loop inside it.
3. 3If it's genuinely slow: cache dependencies, split the job, or parallelize the slowest step.
4. 4Raise timeout-minutes only deliberately, with a comment saying why. A raised limit without a reason is a future 60-minute hang.