Actions stopped working according to schedule

[zakerikk]

Select Topic Area

Bug

Body

Hi,

What happened to github actions schedule?

For April 14, it didn't work or ran only once per hour instead of every 5 minutes, for example:

https://github.com/zakerikk/actions-check/blob/master/.github/workflows/check.yml
https://github.com/zakerikk/actions-check/actions

The status page says all is good with Actions, but I don't agree with that

[lbenz730]

I am having the same issues with my jobs scheduling as well. Not running as scheduled or massive (6+ hour) delays. Glad to hear I am not alone.

[zakerikk]

with this setup:

on:
  workflow_dispatch:
  schedule:
    - cron: '*/5 * * * *' 

Actions were supposed to run 28 times, but they only ran once

[lbenz730]

With this setup, this has yet to be scheduled in almost 3 hours.

name: hello-world
on:
  schedule:
    - cron: "* * 15 * *"
  workflow_dispatch:
jobs:
  my-job:
    runs-on: ubuntu-latest
    steps:
      - name: my-step
        run: echo "Hello World!"

https://github.com/lbenz730/fantasy_baseball/actions/workflows/hello_world.yml

[narugo1992]

im also facing similar issues, im syncing data with github action, use something like 0 * * * *, but huge delay in recent 1 day. often delay for several hours.

one task with 0 */1 * * *

another task with */15 * * * *

[humzam]

We are also facing the same issue in our company's GitHub Enterprise Cloud account.

No changes, and the trigger suddenly stopped working. Manual execution of the workflow works with no issues.

[fasatrix]

same here I am facing the same issue

[humzam]

Update: At least in our case, we figured out the issue with some help from enterprise GitHub support.

Apparently the GHA workflow's ability to execute the schedule is tied specifically to the individual user who created the workflow or last made a commit to the cron schedule line of the file.

We had an employee leave the company who wrote our cron workflow. By making a commit to modify the cron schedule in the workflow file, the automated schedule trigger came back to life.

What a strange bug. Hope this helps others!

[katsiaryna-firsava-epam]

Hi, can you please make a note in the official documentation about this point,I had the same issue and spent some time finding an answer in the reported issues. It will be much easier if we have it marked in the official docs. Thanks in advance.

[humzam]

It seems the documentation does have this covered, perhaps it was added later.

For an enterprise with Enterprise Managed Users, scheduled workflows will not run if the last actor associated with the scheduled workflow has been deprovisioned (and therefore become suspended) by the Enterprise Managed User identity provider (IdP).