Scheduled Jobs Skipped?

Was there an infrastructure issue a few days ago that prevented scheduled jobs from running?

I’m asking because I don’t see any evidence of this scheduled job being run on the 18th.

Workflow: https://github.com/zapbot/zap-mgmt-scripts/blob/742d9a8c1170634ff5d135a38848f69f129a69a7/.github/workflows/record-stats.yml, as you can see it hasn’t been changed in 22 days. The schedule is set for midnight:

on:
  schedule:
    - cron:  '0 0 * * *'

But there’s no “3 days ago” run at all:

Is there no assurance on execution of scheduled jobs? I mean if they aren’t executed with in n time (window) of their scheduled time are they abandon? Could there have been some sort of GitHub Actions resource contention issue that caused them not to run/fire and then the window was passed?

Thanks for letting us know that you reposted something @kingthorin.

In the future, instead of reposting something, you can flag your own post and ask the moderator team to move it between categories. Since you’ve reposted this, I’m going to close this older copy in favor of the newer one.

1 Like