GitHub Actions schedule trigger never runs, but workflow_dispatch works

[yosuk-sitewatcher]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

ARC (Actions Runner Controller)

Discussion Details

Repository: yosuk-sitewatcher / SiteWatcher

I have a GitHub Actions workflow where workflow_dispatch works correctly, but schedule never triggers.

Workflow file:
.github/workflows/sitewatcher.yml

Current workflow:

name: SiteWatcher Monitor

on:
workflow_dispatch:
schedule:
- cron: "*/10 * * * *"

jobs:
run:
runs-on: ubuntu-latest

steps:
  - name: Checkout
    uses: actions/checkout@v4

  - name: Setup Python
    uses: actions/setup-python@v5
    with:
      python-version: "3.14"

  - name: Install dependencies
    run: |
      pip install .

  - name: Run SiteWatcher
    env:
      EMAIL_HOST: ${{ secrets.EMAIL_HOST }}
      EMAIL_USER: ${{ secrets.EMAIL_USER }}
      EMAIL_PASSWORD: ${{ secrets.EMAIL_PASSWORD }}
      EMAIL_TO: ${{ secrets.EMAIL_TO }}
    run: |
      python src/sitewatcher/main.py

Confirmed:

• workflow_dispatch runs successfully.
• The Python application works correctly when manually triggered.
• Email sending works correctly.
• Secrets are configured correctly.
• The workflow is enabled.
• The workflow file exists in .github/workflows/ on the default branch.
• GitHub Actions recognizes the workflow file.
• I committed changes after modifying the workflow.
• I disabled and re-enabled the workflow.

I tested several schedule intervals:

• ---

• */5 * * * *
• */10 * * * *

However, no scheduled workflow runs have ever been created.

Only manually triggered runs appear.

The workflow seems to be valid, but the schedule event itself does not appear to be firing.

Is there any GitHub-side issue, synchronization problem, or condition that could prevent a schedule trigger from being registered while workflow_dispatch works normally?

Thank you.

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