Scheduled workflows are not being registered (only workflow_dispatch is recognized)

[JaeyongChoi4666]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

Hello GitHub Support team,

I am experiencing an issue where the schedule trigger is not being recognized in my private repository.

Repository details

Repository: JaeyongChoi4666/AutoCountReviewers

Visibility: Private

Default branch: main

Workflow files: Located under .github/workflows/

Example workflow: schedule-smoke-2.yml

Problem description

The workflow YAML contains both workflow_dispatch and schedule triggers, for example:

name: schedule-smoke
on:
schedule:
- cron: '*/5 * * * *'
workflow_dispatch:
jobs:
ping:
runs-on: ubuntu-latest
steps:
- run: echo "event=${{ github.event_name }}"

However, on the workflow page, GitHub only shows:

“This workflow has a workflow_dispatch event trigger.”

The schedule trigger is not listed at all.

As a result, no runs are ever created with event: schedule, even after waiting for multiple cron intervals.

I have already confirmed:

Repository is not a fork

Workflow is on the default main branch

Actions are enabled (“Allow all actions and reusable workflows” is selected)

Sufficient Actions minutes are available (usage well below quota)

Manual dispatch works fine

Screenshots

Expected behavior

The workflow page should display:

“This workflow has a `workflow_dispatch and schedule event trigger.”

Scheduled runs (event: schedule) should appear according to the cron definition.

Request

Could you please check why the schedule event is not being registered in this repository?
Is this a known issue or misconfiguration?

Thank you in advance!

[Dee570]

Looks like GitHub isn’t showing your schedule because of a small YAML thing. Make sure schedule: is properly indented under on:. Like this:

name: schedule-smoke
on:
  schedule:
    - cron: '*/5 * * * *'
  workflow_dispatch:
jobs:
  ping:
    runs-on: ubuntu-latest
    steps:
      - run: echo "event=${{ github.event_name }}"

YAML is picky with spaces, that’s often why schedules don’t show. Sometimes the UI just takes a bit to display it, but the workflow should still run on the next cron.

Also, making a tiny commit to the workflow can help GitHub pick it up.

[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! 💬