Scheduled workflow is not running anymore

[dorienmc]

Select Topic Area

Question

Body

I have encountered strange behaviour for one of my (daily) scheduled workflows, a month ago it suddenly stopped running.
This is strange because;

1. The workflow is not disabled
2. It's on a private organizational repository (so automatic disable should not be done by github)
3. A similar workflow (different parameters, different cron time) does run daily
4. The latest commit/PR on the repository was on July 5th (so way less than 60 days ago)
5. The same workflow on different repositories does run daily
6. The workflow syntax has not changed (latest change was on May 4th)
7. The last run (on July 3th) was successful (and so where at least the 10 before that)

It's not like the schedule event is triggered and the flow fails, the schedule event is never even triggered.
Note that it uses cron: '0 12 * * 1-5' which is considered a peak hour, but so do our other repositories (about 10 of them) and those all run fine. It's neither a point of permissions, as a similar workflow (see point 3) runs fine. And in that case I would expect it to fail instead of not be triggered at all.

More on point 2
This workflow does run daily

# ./github/workflows/deploy-production.yml
name: Daily deploy to production

on:
  schedule:
    # Deploy every weekday at 08:00 UTC
    - cron: '0 8 * * 1-5'

jobs:
  deploy:
    uses: '<internal organization repo>/.github/workflows/deploy.yml@main'
    secrets: inherit
    with:    
      environment: production

But this workflow does one not

# ./github/workflows/deploy-staging.yml
name: Daily deploy to staging

on:
  schedule:
    # Deploy every weekday at 12:00 UTC
    - cron: '0 12 * * 1-5'

jobs:
  deploy:
    uses: '<internal organization repo>/.github/workflows/deploy.yml@main'
    secrets: inherit
    with:    
      environment: staging

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[ThibauldC]

Did you ever solve this @dorienmc ? We are facing the same issue