Scheduled workflows stopped firing after workflow file replacement — workflow_dispatch still works

[ibtake]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

A weekly scheduled workflow (cron 45 4 * * 1 with timezone: America/Sao_Paulo) ran
reliably since August 2026.

On Oct 2 I pushed a new version of the same workflow file. The trigger block is
unchanged — only the job's env vars and steps changed (added a second storage
destination). Since that push, no scheduled run fires at all: nothing appears in
the Actions tab — not queued, not failed, simply no run created. Meanwhile,
workflow_dispatch runs work perfectly.

What I already checked / tried

• Workflow file exists on the repository's default branch; the workflow is listed
  in the Actions sidebar and enabled.
• Removed the timezone key and set the cron in plain UTC — no change.
• Created a brand-new minimal test workflow (only an echo step) with
  */5 * * * * — it also never fires, not even once, for 2+ hours.
• Pushed new commits to the default branch after the change (the documented
  "resync" fix from the January incident) — no effect.
• concurrency group unchanged from the previously working version.
• No fork; Actions permissions = "Allow all actions"; repo is private.
• githubstatus.com shows Actions operational, no incidents.

Current trigger block:

on:
  schedule:
    - cron: '45 4 * * *'
      timezone: 'America/Sao_Paulo'
  workflow_dispatch:

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