Scheduled jobs are not running on time

I set cron string to */5 * * * * but the task is run nearly every 10 mins, contrary to what is defined as the minimum interval (5 mins).

Workflow file:

name: Run periodically.

on:
  schedule:
    - cron: '*/5 * * * *'

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v2
    - uses: actions/setup-node@v1
    - run: npm i
    - run: node index.js
2 Likes

Sorry for letting you suffering from this. This is a known issue. And I found an issue in our internal channel: due to the large number of scheduled jobs, It is beyond the current process rate of scheduled jobs. So there are some delay. Also we know that it bring significant pain for our customers. GitHub engineering team are working on a way to resolve this issue and improve schedule job behavior. Thanks for your understanding.

1 Like

I mean, running every 5 minutes is fairly extensive. I am willing to bet they will end up making it a 15 minute minimum.

Any update on this? I set up a job at 06:30 but it starts at 06:44 (GMT both).
Or is this feature dying from success? If I go premium would GHA run in time?

I wanted to report that this issue is still very much alive a year after being reported here. A '*/5 * * * *' cron schedule for an action varies wildly from a five minute tick. Just in the last 24 hours I’ve seen the 5 minutely job run anywhere from 6 to 45 minutes between runs.

While the job should be running 12 times per hour, I don’t think I’ve ever seen it run more than 5 or 6 times in a one hour period.

If the system is unable to operate reliably, you should at least put a warning in the schedule docs to indicate that running on schedule is more of an aspiration, and should not be expected in practice.

You seem to imply this is a scaling issue, which if true has been present for a very long time. Strangely though, if I manually trigger an action via UI or a push it always runs within seconds of the trigger. So this clearly seems to be an issue only with cron triggers.

I hope you can raise this issue again.

Cheers.