Changing Cron Schedule Does Not Update Next Run Time #280

Closed
opened 2026-02-05 17:23:05 +03:00 by OVERLORD · 0 comments
Owner

Originally created by @SJ-Tom on GitHub (Mar 21, 2025).

Originally assigned to: @Boy132 on GitHub.

Current Behavior

If I create a schedule with 0 3 * * *, the next run correctly shows 2025-03-22 03:00:00. However, when I update the schedule to 0 2 * * *, the next run time does not update and still shows 2025-03-22 03:00:00 instead of the expected 2025-03-22 02:00:00.

Expected Behavior

When changing the cron schedule, the next run time should update accordingly. In this case, after modifying the schedule to 0 2 * * *, the next run should be 2025-03-22 02:00:00.

Steps to Reproduce

  1. Create a new schedule with a cron expression (e.g., 0 3 * * *) and save/close it.
  2. Edit the same schedule and change the cron expression to a different time (e.g., 0 2 * * *), then save/close it.
  3. Observe that the next run time is not updated to reflect the new schedule.

Panel Version

1.0.0-beta18

Wings Version

1.0.0-beta10

Games and/or Eggs Affected

Minecraft (Paper)

Docker Image

ghcr.io/parkervcp/yolks:java_21

Error Logs


Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @SJ-Tom on GitHub (Mar 21, 2025). Originally assigned to: @Boy132 on GitHub. ### Current Behavior If I create a schedule with `0 3 * * *`, the next run correctly shows `2025-03-22 03:00:00`. However, when I update the schedule to` 0 2 * * *`, the next run time does not update and still shows `2025-03-22 03:00:00` instead of the expected `2025-03-22 02:00:00`. ### Expected Behavior When changing the cron schedule, the next run time should update accordingly. In this case, after modifying the schedule to `0 2 * * *`, the next run should be `2025-03-22 02:00:00`. ### Steps to Reproduce 1. Create a new schedule with a cron expression (e.g., `0 3 * * *`) and save/close it. 2. Edit the same schedule and change the cron expression to a different time (e.g., `0 2 * * *`), then save/close it. 3. Observe that the next run time is not updated to reflect the new schedule. ### Panel Version 1.0.0-beta18 ### Wings Version 1.0.0-beta10 ### Games and/or Eggs Affected Minecraft (Paper) ### Docker Image ghcr.io/parkervcp/yolks:java_21 ### Error Logs ```bash ``` ### Is there an existing issue for this? - [x] I have searched the existing issues before opening this issue. - [x] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [x] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD added the 🟢 easy label 2026-02-05 17:23:05 +03:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#280