Github Action Corn job stopped triggering

[lanadeldri]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

My github action has scheduled corn job every Monday and Thursday. I was working fine for 2-3 weeks.

Last time it got triggered was last Monday, then last Thursday was not triggered.

No changes to .yml file. What happened here?

[github-actions[bot]]

💬 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 ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

[JEETJM]

This can happen with scheduled GitHub Actions even when the workflow file hasn't changed.

A few things I would check:

• Make sure the workflow is still enabled and the repository hasn't had recent activity restrictions.
• Check the Actions → workflow → scheduled runs to see whether GitHub created the scheduled run but failed to start the job.
• Verify the cron expression and timezone. GitHub Actions cron schedules use UTC.
• Scheduled workflows can occasionally be delayed or skipped due to GitHub Actions load.
• If the workflow hasn't run for a while, try making a small commit to the default branch and see whether the next scheduled run works.

For example:

on:
  schedule:
    - cron: '0 0 * * 1,4'

This runs every Monday and Thursday at 00:00 UTC.

If the next scheduled run is also missed, checking the repository's Actions logs and GitHub Status would help determine whether it's a workflow configuration issue or a GitHub-side problem.