Action schedule #14495

New Issue

GiteaMirror · 2025-11-02T11:14:30-06:00

GiteaMirror commented

2025-11-02 11:14:30 -06:00

Originally created by @top-psi on GitHub (May 15, 2025).

Description

When I configure a action schedule on the default branch development like this:

name: Scheduler Development
--
  | run-name: Scheduler Development
  | on:
  | workflow_dispatch:
  | schedule:
  | - cron: "0 1 * * *"

And check the Database about the scheduler entry, it stays empty.

When I migrate same repo to our test Server running 1.24.0 RC0 the schedule appears instantly.

I am aware that workflow_dispatch is not there yet but it doesn't affect the issue.
Same configuration in any repo (personal or organization) creates a DB entry.

I check the DB with following command:
SELECT * FROM action_schedule_spec;

Gitea Version

1.23.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.47.2

Operating System

RHEL 9

How are you running Gitea?

Docker deployed with ansible

Database

PostgreSQL

Originally created by @top-psi on GitHub (May 15, 2025). ### Description When I configure a action schedule on the default branch development like this: ``` name: Scheduler Development -- | run-name: Scheduler Development | on: | workflow_dispatch: | schedule: | - cron: "0 1 * * *" ``` And check the Database about the scheduler entry, it stays empty. When I migrate same repo to our test Server running 1.24.0 RC0 the schedule appears instantly. I am aware that workflow_dispatch is not there yet but it doesn't affect the issue. Same configuration in any repo (personal or organization) creates a DB entry. I check the DB with following command: `SELECT * FROM action_schedule_spec;` ### Gitea Version 1.23.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.47.2 ### Operating System RHEL 9 ### How are you running Gitea? Docker deployed with ansible ### Database PostgreSQL

GiteaMirror added the topic/gitea-actions type/bug labels 2025-11-02 11:14:30 -06:00

GiteaMirror closed this issue

2025-11-02 11:14:31 -06:00

GiteaMirror commented

2025-11-02 11:14:31 -06:00

@abrain commented on GitHub (Jul 17, 2025):

We successfully used the cron schedule on Gitea 1.23.7. With the upgrade to 1.24.2, we removed the schedule to trigger the workflow dynamically via the API. When we wanted to re-introduce the cron schedule later, it no longer triggered any workflow runs.

@abrain commented on GitHub (Jul 17, 2025): We successfully used the cron schedule on Gitea 1.23.7. With the upgrade to 1.24.2, we removed the schedule to trigger the workflow dynamically via the API. When we wanted to re-introduce the cron schedule later, it no longer triggered any workflow runs.

GiteaMirror commented

2025-11-02 11:14:31 -06:00

@abrain commented on GitHub (Jul 21, 2025):

Oddly enough, the cron schedule started working a few days later.

A look into the database confirms, that the action schedule only was created after another Pull Request (which was completely unrelated to workflows) was merged. The commit_sha in the action_schedule table points to that commit, and not the one that added the schedule in the first place.

I was able to reproduce the bug by adding the cron schedule through a Pull Request and merging it with "Fast-forward only". This does not create an entry in action_schedule or action_schedule_spec.

@abrain commented on GitHub (Jul 21, 2025): Oddly enough, the cron schedule started working a few days later. A look into the database confirms, that the action schedule only was created after another Pull Request (which was completely unrelated to workflows) was merged. The `commit_sha` in the `action_schedule` table points to that commit, and not the one that added the schedule in the first place. I was able to reproduce the bug by adding the cron schedule through a Pull Request and merging it with "Fast-forward only". This does not create an entry in `action_schedule` or `action_schedule_spec`.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14495