actions / actions/runner

No trigger for scheduled cron task in Github actions on a self-hosted runner

Open
#4,210 28 comments 24 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
6.3k
Forks
1.4k
Avg merge
1d 16h
Merged PRs (30d)
24

Description

Describe the bug
When setting up a scheduled task using a cron expression in a Github action, the scheduled task would not trigger. Problem is reported by multiple people on the discussions forum
https://github.com/orgs/community/discussions/185024

To Reproduce

  1. Make an action such as (a small time-granularity is picked)
name: Test Schedule Self Runner

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

jobs:
  test-scheduler:
    runs-on: [Some label]
    steps:
      - name: Echo testing message
        run: echo "Scheduler is working!"
        shell: pwsh
  1. Ensure the action is on the default branch
  2. Ensure the runner is idle
  3. Wait for scheduled time
  4. Notice absence of any log

Expected behavior
A log in the actions tab showing the scheduled task has been triggered.

Runner Version and Platform

Version of your runner?
Self-hosted Workstation

OS of the machine running the runner? Windows 11

What's not working?

Scheduled task being activated and executed when the time condition for triggering is met.

Job Log Output

Absence of log files due to no trigger of the scheduled task.

Runner and Worker's Diagnostic Logs

Complete absence of the trigger for scheduled tasked from the logfiles.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the scheduled workflow example and verify the default-branch, idle-runner, cron, and workflow_dispatch conditions described in the reproduction steps. Compare the Actions tab with the self-hosted runner and worker diagnostic logs; done means identifying why no scheduled run is created or executed and confirming a scheduled run appears.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, powershell
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.