Replies: 5 comments 2 replies
|
💬 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. ⭐ |
|
Hi @Shibly6, Your workflow configuration is syntactically correct and both workflows are confirmed active in the GitHub API ( 1. Scheduler Batch Registration Latency (<24h Old Repositories)In repositories created very recently (your repo was created Nov 15 and GitHub’s cron dispatch backend runs a batch ingestion pipeline that registers new repository cron entries into the runner table on a periodic cycle (often taking 1 to 2 hours to initialize after the file is first pushed). 2. High-Frequency Jitter and Re-Commit Resets
Recommended Next Steps to Verify
Hope this clarifies why the initial scheduled runs are delayed! If this resolves the mystery for you, please feel free to mark this as the accepted answer. |
|
Thanks for the suggestions. Before I make further changes, could you provide:
I want to avoid making speculative changes without evidence. The workflow is valid, manual dispatch works, and the schedule API still returns zero scheduled runs. Thanks! |
|
Hi @Shibly6, Your empirical diagnostic data—specifically that 1. Scheduler Event Creation vs. Runner AssignmentIt is helpful to separate GitHub Actions' execution lifecycle into two distinct phases:
Because your API query returns 2. Documented Cause: The Scheduled Workflow Actor & Write PermissionsUnder GitHub's documented execution model for scheduled events:
Unlike If GitHub's internal authorization check encounters any of the following for that actor when evaluating the schedule, event creation fails silently:
3. Recommended Controlled Diagnostic TestTo test whether the cron trigger registry has an actor or registration desync:
If |
|
Thanks everyone for the suggestions. I tried disabling and re-enabling the workflows, but GET /actions/runs?event=schedule still returns total_count: 0, while workflow_dispatch works fine. I couldn't find GitHub documentation backing the indentation or account-restriction explanations, so I'm not changing anything else. As a workaround I've moved to an external trigger (workflow_dispatch from cron-job.org). I'm leaving this unresolved since the root cause of the missing schedule events is still unknown. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello GitHub Team,
I am experiencing an issue where scheduled GitHub Actions workflows are not triggering in my public repository.
Repository: Shibly6/threat-briefing
Affected workflows:
.github/workflows/daily_briefing.yml.github/workflows/schedule-check.ymlEnvironment:
workflow_dispatch: SuccessfulSchedule configuration (test workflow):
Observed behavior:
event=schedule.Could you investigate whether there is a scheduler registration or event delivery issue affecting this repository?
Thank you.
All reactions