You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both succeeded and are attributed to kace03. There were 96 other nominal five-minute slots between them without corresponding run records. Jobs start promptly once a run is created, so this appears to occur before runner execution.
Checks already completed:
Manual dispatch and push execution work.
The scheduled workflow was recreated separately from the application workflow.
The original step-based cron and the current explicit minute list were both tested.
The workflow was disabled/re-enabled, and its cron was edited in a fresh owner-attributed commit.
An independent minimal workflow with no checkout, application code, dependencies, mail or external API requests also produced no scheduled event during its test window; its push execution succeeded.
The public REST API and connected-tool results agreed on the missing scheduled runs. No cancelled or queued scheduled runs explained the gap.
We understand that schedules are best effort and events may be delayed or dropped. We have not established why this repository experiences multi-hour gaps.
Could GitHub check scheduled-event generation and delivery for workflow ID 421809327, whether any triggers were suppressed before run creation, and whether a repository/account eligibility constraint applies? We have no evidence confirming any account restriction.
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestionAsk and answer questions about GitHub features and usageSchedule & Cron JobsTopics about scheduled workflows, cron timing, and related scheduling concerns in GitHub Actions.Welcome 🎉Used to greet and highlight first-time discussion participants. Welcome to the community!source:uiDiscussions created via Community GitHub templates
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Schedule & Cron Jobs
Discussion Details
Repository: https://github.com/kace03/sla-rotterdam
Workflow:
.github/workflows/scheduled-checks.yml— Automatic apartment checksWorkflow ID:
421809327The repository is public, not a fork, not archived, and the workflow is active on the default branch
main. Its current schedule is:At our check on 18 November 2026, the complete run history showed two schedule-triggered runs:
Both succeeded and are attributed to
kace03. There were 96 other nominal five-minute slots between them without corresponding run records. Jobs start promptly once a run is created, so this appears to occur before runner execution.Checks already completed:
We understand that schedules are best effort and events may be delayed or dropped. We have not established why this repository experiences multi-hour gaps.
Could GitHub check scheduled-event generation and delivery for workflow ID
421809327, whether any triggers were suppressed before run creation, and whether a repository/account eligibility constraint applies? We have no evidence confirming any account restriction.All reactions