Skip to content
Discussion options

You must be logged in to vote

Hi @JayChou0609,

Your checks already cover most of the usual configuration issues.

GitHub's documentation confirms that scheduled workflows can be delayed or dropped during periods of high load, especially at the start of an hour.

Since your workflow is active and other scheduled runs are working, I wouldn't assume the YAML is incorrect.

For recovery, one option is to use an external scheduler that checks whether the daily collection completed. If it hasn't, the scheduler could trigger your existing workflow_dispatch through the GitHub API.

You already have a catch-up mechanism, so this could work alongside it without depending entirely on GitHub's cron schedule.

Documentation:
https://do…

Replies: 2 comments

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
0 replies
Answer selected by JayChou0609
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug GitHub or a GitHub feature is not working as intended Actions Build, test, and automate your deployment pipeline with world-class CI/CD Schedule & Cron Jobs Topics about scheduled workflows, cron timing, and related scheduling concerns in GitHub Actions. Welcome 🎉 Used to greet and highlight first-time discussion participants. Welcome to the community! source:ui Discussions created via Community GitHub templates
2 participants