GitHub treats schedule events as best effort, so a heartbeat check that alerts when the job has not checked in is worth adding. Buddy has schedule triggers plus Ping/Website monitoring actions with Slack or Telegram alerts, which covers the silent miss case.

A successful recovery run doesn't necessarily mean the scheduled trigger is working.

I'd check that the workflow is enabled on the default branch, review runs filtered by event=schedule, and verify that the scheduled workflow's associated account is still active.

GitHub notes that scheduled events can be delayed or dropped during high load, especially at the start of an hour. Moving the cron schedule to a less common minute may help.

If scheduled runs remain missing, I'd contact GitHub Support with the workflow name, expected UTC execution times, and relevant run IDs.

Reference: https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows

I'm experiencing a very similar issue with GitHub Actions scheduled workflows since November 2, 2026.

In our repository, which has existed for several years, we have four Full Regression workflows that were successfully triggered by cron schedules during the previous weekend.

On November 2, we updated all four workflows in a single PR to run daily instead of weekly.

Current observations:

• All four scheduled workflows stopped triggering after the cron changes.
• No scheduled runs appear in GitHub Actions history, including when filtering by event=schedule.
• All workflows are enabled and exist on the default branch (main).
• Cron expressions have been verified and are valid.
• Manual workflow execution works successfully.
• We also tried changing the cron execution times and staggering the schedules, but no scheduled executions have appeared.
• Other scheduled workflows (Smoke tests) have previously triggered successfully.

This seems very similar to the issue reported here, especially considering the timing.

Could this be related to a broader GitHub Actions scheduler issue starting on November 2? Is there any known incident or way to verify whether these scheduled events were dropped or never registered?