Errors / checked October 9, 2026

The job has exceeded the maximum execution time of 1m0s

The error

A GitHub Actions run, as a failure annotation on the job, followed by "The operation was canceled." on the step that was running. The time shown is the limit the job hit: 1m0s here comes from timeout-minutes: 1. The run is marked cancelled, not failed.

Quick fix

  1. Check which limit you hit. If the time matches your timeout-minutes, raise it for that job (or for the step with steps[*].timeout-minutes). Without timeout-minutes the default is 360 minutes.
  2. If the job really needs more than 6 hours, split it: GitHub-hosted runners stop every job at 6 hours of execution time whatever timeout-minutes says. Self-hosted runners allow up to 5 days.
  3. If the job usually finishes quickly, look for what hung: a step waiting on input, a network call with no timeout, or a test that never exits. Give those their own timeouts so the job fails with a clear error instead.

RunLater vs GitHub Actions scheduled workflows

Why this happens

GitHub cancels a job when it runs longer than its timeout-minutes (default 360) or the runner's execution limit, whichever comes first. The running step is stopped, its processes are terminated, and the run ends as cancelled.

Source: GitHub Docs: jobs.<job_id>.timeout-minutes

Other solutions

  • A cancelled scheduled run is not retried. The next run happens at the next scheduled time.
  • If the scheduled job only exists to call a URL, it does not need a runner at all. RunLater calls the URL on your cron schedule, waits up to 5 minutes for the response, retries a failed call up to 10 times with exponential backoff, and emails you when a run fails after its retries.

Check a schedule before you deploy it: the cron expression explainer shows the next 10 run times.

Frequently asked questions

What is the default timeout for a GitHub Actions job?

360 minutes (6 hours). It is also the most a job can run on GitHub-hosted runners, so a higher timeout-minutes has no effect there.

Why does the run say cancelled instead of failed?

GitHub cancels the job when the time runs out, so the job and the run both end as cancelled.

How long can a self-hosted runner job run?

Up to 5 days of execution time per job. A workflow run as a whole, including waiting and approvals, can last up to 35 days.

Have the URL called on schedule, with retries

RunLater calls your URL on a cron schedule or at an exact time, in your timezone, retries failed calls with backoff and logs each response, so a timeout or a 5xx shows up in a log instead of disappearing.

Start a 14-day trialStarter is $15/month for 250 scheduled requests and 25,000 runs. Cancel before day 14 and you pay nothing.

Related errors