Github Action Corn job stopped triggering #206358

lanadeldri · 2026-08-31T14:43:06Z

lanadeldri
Aug 31, 2026

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Schedule & Cron Jobs

Discussion Details

My github action has scheduled corn job every Monday and Thursday. I was working fine for 2-3 weeks.

Last time it got triggered was last Monday, then last Thursday was not triggered.

No changes to .yml file. What happened here?

2026-08-31T14:43:46Z

github-actions[bot]
Bot Aug 31, 2026

💬 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 ⏩

Your input will be carefully reviewed and cataloged by members of our product teams.
- Due to the high volume of submissions, we may not always be able to provide individual responses.
- Rest assured, your feedback will help chart our course for product improvements.
Other users may engage with your post, sharing their own perspectives or experiences.
GitHub staff may reach out for further clarification or insight.
- We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

Upvote and comment on other user feedback Discussions that resonate with you.
Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

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. ⭐

0 replies

tomm1990 · 2026-09-02T13:25:53Z

tomm1990
Sep 2, 2026

before guessing “github load” vs a dead schedule registration - need a couple specifics:

what’s the exact on.schedule cron (and any timezone:) from the workflow on the default branch? paste that block.
when thursday’s slot passed, did github create zero event=schedule runs at all, or is there a run sitting queued / waiting / failed? this is the split:

gh api 'repos/OWNER/REPO/actions/runs?event=schedule&per_page=10' \
  --jq '{total_count, runs: [.workflow_runs[]|{id,created_at,status,conclusion,display_title}]}'

is the workflow still active on the default branch, and was last monday’s success the same workflow file/path?

gh api repos/OWNER/REPO/actions/workflows --jq '.workflows[] | select(.path|endswith("YOUR.yml")) | {id,path,state}'

drop those three and we can tell whether you’re in “scheduler never materialized the run” (same bucket as a lot of post-Aug-26 reports) vs something local like utc/timezone or a disabled workflow.

2 replies

lanadeldri Sep 3, 2026
Author

Thanks。

For #1: I am sure it on the default branch as I only have 1 branch which is main

name: CMC SG File Report

on:
  schedule:
    - cron: "13 12 * * 1,4"

  workflow_dispatch:

For #2, GitHub created zero event=schedule runs for the missed slots. The last scheduled run that actually materialized was Aug 24. There is nothing queued, waiting, skipped, or failed for Aug 27 or Aug 31.

For #3, the workflow is still active, and the previous successful scheduled runs use the same workflow path (.github/workflows/main.yml). Manual workflow_dispatch runs on Aug 27 and Aug 31 also completed successfully using that same workflow.

So this looks like the scheduler is not materializing the scheduled runs at all, rather than a job/runner failure.

I also tested by changing the cron to a near-future time and committing it to the default branch, but no scheduled run was created then either.

Here are the raw outputs:

Workflow state:

$ gh api repos/xx/xxx/actions/workflows \
  --jq '.workflows[] | {id,name,path,state}'

{
  "id": 333094355,
  "name": "CMC SG File Report",
  "path": ".github/workflows/main.yml",
  "state": "active"
}

Scheduled runs only:

$ gh api 'repos/xx/xxx/actions/runs?event=schedule&per_page=10' \
  --jq '{total_count, runs: [.workflow_runs[]|{id,created_at,status,conclusion,display_title,path}]}'

{
  "runs": [
    {
      "conclusion": "success",
      "created_at": "2026-08-24T13:00:44Z",
      "display_title": "CMC SG File Report",
      "id": 32730197608,
      "path": ".github/workflows/main.yml",
      "status": "completed"
    },
    {
      "conclusion": "success",
      "created_at": "2026-08-20T12:58:55Z",
      "display_title": "CMC SG File Report",
      "id": 32371700850,
      "path": ".github/workflows/main.yml",
      "status": "completed"
    },
    {
      "conclusion": "success",
      "created_at": "2026-08-17T12:54:31Z",
      "display_title": "CMC SG File Report",
      "id": 32032222262,
      "path": ".github/workflows/main.yml",
      "status": "completed"
    },
    {
      "conclusion": "success",
      "created_at": "2026-08-13T13:23:57Z",
      "display_title": "CMC SG File Report",
      "id": 31704710584,
      "path": ".github/workflows/main.yml",
      "status": "completed"
    }
  ],
  "total_count": 4
}

Recent runs for this exact workflow:

$ gh api repos/xx/xxx/actions/workflows/333094355/runs \
  --jq '.workflow_runs[:10] | .[] | {id,event,created_at,status,conclusion,path}'

{
  "conclusion": "success",
  "created_at": "2026-08-31T14:33:45Z",
  "event": "workflow_dispatch",
  "id": 33403355380,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-27T14:01:39Z",
  "event": "workflow_dispatch",
  "id": 33079966390,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-24T13:00:44Z",
  "event": "schedule",
  "id": 32730197608,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-20T12:58:55Z",
  "event": "schedule",
  "id": 32371700850,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-17T12:54:31Z",
  "event": "schedule",
  "id": 32032222262,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-14T19:05:03Z",
  "event": "workflow_dispatch",
  "id": 31831655531,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-13T15:45:42Z",
  "event": "workflow_dispatch",
  "id": 31717137887,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}
{
  "conclusion": "success",
  "created_at": "2026-08-13T13:23:57Z",
  "event": "schedule",
  "id": 31704710584,
  "path": ".github/workflows/main.yml",
  "status": "completed"
}

The key thing I'm seeing is that scheduled runs existed normally through Aug 24, then stopped being created entirely, while manual dispatches continued to work successfully. Does that point to a dead/stale schedule registration on GitHub's side?

tomm1990 Sep 6, 2026

yeah - that dumps it. this isn’t utc/timezone and it isn’t a broken job.

cron "13 12 * * 1,4" on main is fine (off-peak minute even). workflow 333094355 stays active, same .github/workflows/main.yml. workflow_dispatch succeeded on Aug 27 + Aug 31. schedule history just stops after Aug 24 (32730197608) - zero event=schedule objects for the missed mon/thu slots, and your near-future cron test also created nothing. so the scheduler isn’t materializing runs for this workflow/repo at all.

same shape as a pile of post-Aug-26 reports: push/manual ok, schedule registration dead.

try these in order (low → higher friction):

refresh registration (sometimes enough):

gh workflow disable main.yml --repo OWNER/REPO
gh workflow enable main.yml --repo OWNER/REPO

then wait through a couple 12:13 UTC mon/thu slots (or temporarily set an offset cron like 17,32,47 * * * * to prove faster).

if still total_count stuck at 4 schedule runs forever: rename the file on main (e.g. cmc-sg-file-report.yml) so github mints a new workflow id - disable/enable only flips state, rename often remints the schedule entity.
meanwhile keep using workflow_dispatch (already proven green).

if 1+2 fail, support with this packet:

workflow_id: 333094355
path: .github/workflows/main.yml
state: active
cron: 13 12 * * 1,4 (UTC, no timezone key)
last schedule run: 32730197608 @ 2026-08-24T13:00:44Z
missed: Aug 27 + Aug 31 (+ near-future cron test) - zero event=schedule runs
manual ok: 33079966390 (Aug 27), 33403355380 (Aug 31)
need: refresh/reindex schedule registration for this workflow/repo

so yes - dead/stale schedule materialization on github’s side, not your yaml.

This comment was marked as off-topic.

Sign in to view

Navigation Menu

GitHub Community

Github Action Corn job stopped triggering #206358

Uh oh!

{{title}}

Uh oh!

Replies: 3 comments 2 replies

Uh oh!

{{title}}

Uh oh!

This comment was marked as off-topic.

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

GitHub Community

Github Action Corn job stopped triggering #206358

Uh oh!

lanadeldri Aug 31, 2026

🏷️ Discussion Type

💬 Feature/Topic Area

Discussion Details

Replies: 3 comments · 2 replies

Uh oh!

github-actions[bot] Bot Aug 31, 2026

This comment was marked as off-topic.

Uh oh!

tomm1990 Sep 2, 2026

Uh oh!

Uh oh!

lanadeldri Sep 3, 2026 Author

Uh oh!

tomm1990 Sep 6, 2026

lanadeldri
Aug 31, 2026

Replies: 3 comments 2 replies

github-actions[bot]
Bot Aug 31, 2026

tomm1990
Sep 2, 2026

lanadeldri Sep 3, 2026
Author