Scheduled workflows not being trigerred

[Eduardo-Malo]

Why are you starting this discussion?

Bug

What GitHub Actions topic or product is this about?

General

Discussion Details

Hello,

Scheduled workflows are not being enqueued for my private repository despite the workflow files being present on the default branch and set to active. Manual workflow_dispatch runs work, but no runs with event "schedule" are appearing.

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

[SrRyan]

👋 Thank you for reporting the issue with scheduled workflows not triggering. We identified a related change from last week that was rolled back today. Any commit pushed to the default branch will resync the impacted scheduled workflows and resolve any scheduling issues you may be experiencing. If you continue to experience issues with syncing schedules, please reply with a comment including the following:

1. Impacted repository
2. Workflow path and name
3. Cron syntax in the workflow

Note: Schedules that run during periods of high load (e.g., midnight UTC) may be delayed or, if load is sufficiently high, potentially dropped. Please see our docs for further information.

[Scolliq]

I ran into this too. Scheduled workflows can silently stop running after 60 days of repo inactivity, or sometimes just not trigger reliably.

What I ended up doing is adding a dead man's switch at the end of the workflow — a heartbeat ping to an external monitor. If the ping stops arriving, I get a Slack webhook.

steps:
  - name: Your actual job
    run: ./do-stuff.sh

  - name: Heartbeat
    if: success()
    uses: Scolliq/gabe-action@v1
    with:
      ping-url: ${{ secrets.GABE_PING_URL }}

Gabe is open source and free for 3 monitors. Catches the exact scenario you are describing.