Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Scheduled (
cron) GitHub Actions workflows have never fired on my account, across two different repositories, over a full day of testing. Manualworkflow_dispatchruns of the exact same workflows succeed reliably and quickly every time (typically 1-4 minutes). GitHub Support wouldn't let me raise a ticket for this (I'm on a free personal account), so posting here in case anyone from GitHub or the community has seen this before.Account: created 2026-08-26 (~1 day old at the time of testing)
What I tested:
tjj0rdan/fara-monitor(private):.github/workflows/daily-fetch.yml,cron: "15 7 * * *"— missed its 07:15 UTC production slot on 2026-08-27.scheduler-probe.yml, trivialechojob, its ownscheduletrigger) — did not fire (checked with 30+ min buffer, zero runs of any kind recorded).tjj0rdan/scheduler-scratch-test) created purely to isolate the issue — trivial workflow, ownscheduletrigger — also did not fire (checked with 40+ min buffer).gh run listacross all of the above shows onlyworkflow_dispatch-triggered runs; zeroschedule-triggered runs exist anywhere on this account, on any repo.Ruled out:
active(not disabled) on all tested workflowsactions/permissions:enabled: true,allowed_actions: "all"Given the account age, my working theory is some kind of anti-abuse/trust restriction on scheduled Actions for brand-new accounts, but I can't confirm that from public docs, and Support (via the AI triage) couldn't confirm or deny it either — it explicitly said this would need a human/backend review.
Has anyone seen this before, or know if there's a known ramp-up period for scheduled triggers on new accounts? Happy to provide more detail if useful.
All reactions