GitHub Actions scheduled workflow not triggering — manual dispatch works #213220
Replies: 4 comments 1 reply
|
💬 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 ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
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. ⭐ |
|
Since manual runs work correctly, the issue seems related to GitHub's scheduler rather than your workflow. Try checking whether the account that last modified the cron schedule is still active and has repository access. If scheduled runs still don't appear, contact GitHub Support and ask them to check the schedule registration and associated actor for your repository. |
|
Thank you for your reply. I checked the account associated with the last cron modification. The last commit that changed the schedule was:
The account hturconi77 is active and has access to the repository. I can successfully trigger the workflow manually using workflow_dispatch, and the workflow completes successfully. However, scheduled executions are still not being triggered. I have also disabled and re-enabled the workflow, and changed the cron expression to: 3,18,33,48 * * * * Could GitHub Support please investigate the schedule registration and the associated actor for this repository? In particular, could you verify whether the schedule is correctly registered and whether there is any issue preventing scheduled events from being dispatched? Thank you |
|
Hi @hturconi77 👋 Based on your description, the issue appears to be related to the GitHub Actions Since 1. Verify the actual workflow YAMLMake sure the workflow contains: on:
schedule:
- cron: "3,18,33,48 * * * *"
workflow_dispatch:This is a valid cron expression and should run four times per hour. By default, GitHub Actions uses UTC for scheduled workflows. 2. Check the scheduled workflow actorGitHub documents an important edge case: scheduled workflows may stop triggering if the account associated with the schedule is suspended, deleted, or deprovisioned. This can occur even when the workflow remains enabled and manual executions succeed. A user with repository write access can update the cron expression and commit that change directly to the default branch. For example, temporarily change it to: on:
schedule:
- cron: "7,22,37,52 * * * *"
workflow_dispatch:This may refresh the scheduled workflow's associated actor. Since you've already updated the cron expression, the next important question is whether that change was committed by an active account with write access. 3. Verify workflow registration using GitHub CLIRun: gh api repos/hturconi77/deye-soc-monitor/actions/workflows \
--jq '.workflows[] | {name, path, state, id}'Confirm that Next, check whether GitHub has recorded any scheduled executions: gh run list \
--repo hturconi77/deye-soc-monitor \
--workflow monitor.yml \
--event schedule \
--limit 20If no scheduled runs are returned after multiple expected trigger times, that supports the hypothesis that the problem occurs before job execution. 4. Test with a minimal scheduled workflowAs a diagnostic step, create a separate workflow on the default branch: name: Schedule Diagnostic
on:
schedule:
- cron: "11,26,41,56 * * * *"
workflow_dispatch:
jobs:
test:
runs-on: ubuntu-latest
steps:
- name: Print event details
run: |
echo "Event: $GITHUB_EVENT_NAME"
echo "Actor: $GITHUB_ACTOR"
date -uIf this workflow triggers but the original does not, investigate the original workflow's registration or configuration. If neither workflow triggers, the evidence points more strongly toward a repository-level or scheduler-related issue. 5. Consider GitHub scheduler limitationsGitHub explicitly states that scheduled workflows:
However, consistently missing every scheduled execution is different from an occasional scheduling delay. 6. Escalate with diagnostic evidenceIf both scheduled workflows fail to trigger, I recommend contacting GitHub Support: Include:
One additional note: Actions Runner Controller (ARC) handles runner orchestration. If no workflow run is ever created, the issue is likely upstream of runner assignment, making schedule registration a more relevant area to investigate. Official documentation: https://docs.github.com/en/actions/how-tos/troubleshoot-workflows I hope this helps narrow down the issue! |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Bug
💬 Feature/Topic Area
ARC (Actions Runner Controller)
Discussion Details
Hello GitHub Actions team,
I am experiencing an issue with a scheduled GitHub Actions workflow that never triggers automatically, although manual runs work correctly.
Repository: hturconi77/deye-soc-monitor (private repository)
Default branch: main
Workflow name: Deye SOC monitor
Workflow file: .github/workflows/monitor.yml
Current schedule configuration:
on:
schedule:
- cron: "3,18,33,48 * * * *"
workflow_dispatch:
What I have verified:
The repository is private and main is the default branch.
The workflow file exists on the default branch.
The workflow is enabled.
Manual workflow_dispatch executions complete successfully.
The Python monitor runs correctly, retrieves data from the Deye API, updates the repository state file, and sends notifications through ntfy.
The Scriptable widget also updates correctly after a manual run.
No scheduled (schedule) executions appear in the Actions history.
I changed the cron expression to avoid minute 00 and re-registered the schedule.
I also disabled and re-enabled the workflow, but the issue persists.
The last successful manual execution confirms that the workflow itself and its dependencies are working. The problem appears to be specifically related to GitHub's scheduled event triggering or schedule registration.
Could you please investigate whether the scheduled workflow is correctly registered and whether there is any issue with its associated actor or the scheduling service?
Since this is a private repository, I can provide the workflow file and any additional diagnostic information through an appropriate channel.
Thank you for your help.
All reactions