GitHub Actions Job Timeout — 'Exceeded Maximum Execution Time of 360 Minutes'

What this error means

The job was cancelled because it exceeded the maximum timeout period of 360 minutes is a GitHub Actions failure pattern reported for developers trying to resolve github actions workflow cancellation due to 6-hour hard timeout limit on hosted runners. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

Validated from markaicode.com guide (fetched at 2026-05-21T10:02:48Z) and fixdevs.com guide (fetched at 2026-05-21T10:02:51Z). Two independent sources confirm the exact error string. Not in covered-errors.md (which only lists npm ci, Node version mismatch, and permission denied). Targets long-running CI/CD pipelines for enterprise teams — high commercial value.

Common causes

• Validated from markaicode.com guide (fetched at 2026-05-21T10:02:48Z) and fixdevs.com guide (fetched at 2026-05-21T10:02:51Z). Two independent sources confirm the exact error string. Not in covered-errors.md (which only lists npm ci, Node version mismatch, and permission denied). Targets long-running CI/CD pipelines for enterprise teams — high commercial value.

Quick fixes

1. Confirm the exact error signature matches The job was cancelled because it exceeded the maximum timeout period of 360 minutes.
2. Check the GitHub Actions account, local tool state, and provider configuration involved in the failing workflow.
3. Compare the failing environment with a known working setup, then change one configuration value at a time.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://markaicode.com/errors/github-actions-timeout-error-fix-production/
• https://fixdevs.com/blog/github-actions-timeout/

Evidence note: Validated from markaicode.com guide (fetched at 2026-05-21T10:02:48Z) and fixdevs.com guide (fetched at 2026-05-21T10:02:51Z). Two independent sources confirm the exact error string. Not in covered-errors.md (which only lists npm ci, Node version mismatch, and permission denied). Targets long-running CI/CD pipelines for enterprise teams — high commercial value.

Related errors

• GitHub Actions

FAQ

What should I check first?

Start with the exact The job was cancelled because it exceeded the maximum timeout period of 360 minutes text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed GitHub Actions workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without The job was cancelled because it exceeded the maximum timeout period of 360 minutes.