Yes, another Scheduled workflow that never fires

[Sig2018]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

The schedule trigger of one workflow has never fired in a brand-new private repository (Free plan, personal account). workflow_dispatch runs work fine every time. The REST API returns total_count: 0 for event=schedule.

Setup

• Repo: Sig2018/conciertos-script (private, not a fork, personal account, no organization)
• Created: 2026-10-07 02:37 UTC
• Workflow: .github/workflows/actualizar.yml (workflow id 377014257), on the default branch main, state active
• Plan: GitHub Free (usage is tiny: ~20 s per run)
• Triggers:

on:
  schedule:
    - cron: "17 * * * *"     # was "15 9,21 * * *" at first; hourly only for this test
  workflow_dispatch:
permissions:
  contents: write

What I observed

- workflow_dispatch runs succeed (4 successful runs so far; last one 2026-10-07 21:33 UTC).
- GET /repos/Sig2018/conciertos-script/actions/runs?event=schedule → total_count: 0.
- The original schedule (15 9,21 * * *) never fired: the 2026-10-07 09:15 UTC slot produced no run.
- After changing it to 17 * * * * (commit pushed to main at 14:06 UTC), I waited through the :17 slots at 14, 15, 16, 17, 18, 19, 20 and 21 UTC. No scheduled run was created in any of them.

What I already tried

1. Pushed commits to main that modify the workflow file (including the cron change above).
2. Disabled and re-enabled the workflow through the API (PUT .../actions/workflows/377014257/disable then /enable, 2026-10-07 ~19:37 UTC).
3. Turned Actions off and on again in the repository settings (Settings → Actions → General), later the same evening.
4. Avoided the top of the hour (minute 15 / 17).

None of these changed anything.

Questions

- Is there a known issue with the scheduler not registering cron triggers for new private repositories on the Free plan?
- Is there anything on my side that would prevent schedulI found nothing: workflow valid, active, on the default branch, not a fork)?
- Is there a way to get the scheduler to re-sync this rep

This looks the same as #202602, #201436, #209473 and #209
Thanks in advance for any help you may have!

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