starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-20 11:20:31 +03:00
Code Issues 42 Packages Projects Releases 12 Wiki Activity

Schedules stuck in processing state after first action #307

New Issue
Closed
opened 2026-02-04 17:28:06 +03:00 by OVERLORD · 4 comments
OVERLORD commented 2026-02-04 17:28:06 +03:00
Owner
Copy Link

Originally created by @Awhikax on GitHub (Apr 12, 2025).

Current Behavior

After the latest update, schedules (both automatic and manually triggered) get stuck in a processing state after executing only the first action. The schedule status in DB is properly updated to is_processing=1 and the first action executes successfully, but subsequent actions are not executed, leaving the schedule in a permanent processing state.

Schedules with a single action are not affected.

Image
Image

Expected Behavior

When a schedule is triggered (manually or automatically), all actions in the schedule should execute sequentially from start to finish. After all actions are completed, the schedule should return to a non-processing state (is_processing=0).

Steps to Reproduce

  1. Create a schedule with multiple actions
  2. Trigger the schedule (manually or wait for automatic execution)
  3. Observe that only the first action executes
  4. Observe that the schedule remains in "Processing" state indefinitely

Note that this has been reproduced on my environment AND on https://demo.pelican.dev/

Panel Version

1.0.0-beta19

Wings Version

1.0.0-beta11

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 @Awhikax on GitHub (Apr 12, 2025). ### Current Behavior After the latest update, schedules (both automatic and manually triggered) get stuck in a processing state after executing only the first action. The schedule status in DB is properly updated to `is_processing=1` and the first action executes successfully, but subsequent actions are not executed, leaving the schedule in a permanent processing state. Schedules with a single action are not affected. ![Image](https://github.com/user-attachments/assets/ddb88354-59cd-4acd-b358-a75e237341e4) ![Image](https://github.com/user-attachments/assets/478c1e8a-6d2f-4a32-9a41-d63d902cbf04) ### Expected Behavior When a schedule is triggered (manually or automatically), all actions in the schedule should execute sequentially from start to finish. After all actions are completed, the schedule should return to a non-processing state (`is_processing=0`). ### Steps to Reproduce 1. Create a schedule with multiple actions 2. Trigger the schedule (manually or wait for automatic execution) 3. Observe that only the first action executes 4. Observe that the schedule remains in "Processing" state indefinitely Note that this has been reproduced on my environment AND on https://demo.pelican.dev/ ### Panel Version 1.0.0-beta19 ### Wings Version 1.0.0-beta11 ### 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 commented 2026-02-04 17:28:26 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Apr 12, 2025):

Probably caused by #1045:
82409f2fba (diff-42070b6867eb63f7f272e859f80f9c341032ffaa2e77e3c0247d47f633316c53) Nope

It's a problem with the queue worker, it sometimes hangs?
When manually running php artisan queue:work the problem doesn't occur.

@Boy132 commented on GitHub (Apr 12, 2025): ~~Probably caused by #1045: https://github.com/pelican-dev/panel/commit/82409f2fba93906e37cd6861b4649269b6e19335#diff-42070b6867eb63f7f272e859f80f9c341032ffaa2e77e3c0247d47f633316c53~~ Nope It's a problem with the queue worker, it sometimes hangs? When manually running `php artisan queue:work` the problem doesn't occur.
OVERLORD commented 2026-02-04 17:28:33 +03:00
Author
Owner
Copy Link

@Awhikax commented on GitHub (Apr 14, 2025):

I'm adding this to the ticket: single task automatic schedule failed while it did work when running it manually. Still no relevant logs.
Image

@Awhikax commented on GitHub (Apr 14, 2025): I'm adding this to the ticket: single task automatic schedule failed while it did work when running it manually. Still no relevant logs. ![Image](https://github.com/user-attachments/assets/f098e079-9800-4f1f-9700-427c5a077b3e)
OVERLORD commented 2026-02-04 17:28:37 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (May 13, 2025):

I can't reproduce it anymore in my local setup or on the demo. @Awhikax , can you please check again on your end?

@Boy132 commented on GitHub (May 13, 2025): I can't reproduce it anymore in my local setup or on the demo. @Awhikax , can you please check again on your end?
OVERLORD commented 2026-02-04 17:28:44 +03:00
Author
Owner
Copy Link

@Awhikax commented on GitHub (May 13, 2025):

I've just upgraded my environment to latest and I'm no longer reproducing either.
@Boy132 I'll let you choose the close reason between completed/not planned.

@Awhikax commented on GitHub (May 13, 2025): I've just upgraded my environment to latest and I'm no longer reproducing either. @Boy132 I'll let you choose the close reason between completed/not planned.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#307
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?