Scheduled (cron) workflow runs deviate significantly from the configured schedule #199278
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
My workflow is configured to run hourly, but actual run start times drift substantially from the scheduled time over the last few days.
What I've configured
Schedule:
Expected
An hourly trigger at (or close to) the configured minute each hour.
Actual
Here is the actual execution for the last couple of days:
What I've tried
0 * * * *→37 * * * *) to avoid the load spike — no observable improvement.Environment
Question
Is this within the expected best-effort behavior for scheduled workflows, and if so, what delay range should I plan around? Is there anything in my config causing extra drift beyond the documented high-load delays?
Beta Was this translation helpful? Give feedback.
All reactions