Skip to content
This repository was archived by the owner on Jul 10, 2026. It is now read-only.
This repository was archived by the owner on Jul 10, 2026. It is now read-only.

Scheduled tasks do not get properly updated in the database #75

Description

@blitzdose

Current Behavior

I have a few schedules configured, all with a single task: Creating a backup. However, while the first run works without a problem, it never runs the task again, because the field is_processing in the tasks table stays on 1 even after a successful run.

Expected Behavior

It looks like the code never updates the database itself when resetting the is_processing field. The corresponding line only updates the task object in PHP, but does not touch the database:

$this->task->update(['is_processing' => false]);

I don't know everything about this codebase, but changing the above line to the following, fixes the issue:

Task::where('id', $this->task->id)->update(['is_processing' => false]);

Steps to Reproduce

  1. Create a schedule with a backup task
  2. Run the schedule
  3. Try to run the schedule again

Panel Version

5.0.5

Panel Installation Type

  • Official Panel Docker image.
  • native install for Panel.
  • I used a third party installation script or Docker image.

Daemon Version

1.3.0

Daemon Installation Type

  • Offical Docker image.
  • Native install.
  • Pyrodactyl Elytra
  • Pterodacty Wings
  • I used a third party installation script or Docker image.
  • Daemon Version does not apply to this Bug

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

After the first successful run, the following message appears in the logs, because is_processing is still set to 1:

[2026-06-07 04:00:03] production.WARNING: Backup task already processing, skipping {"task_id":33,"schedule_id":21,"server_id":8}
[2026-06-07 06:00:06] production.WARNING: Backup task already processing, skipping {"task_id":34,"schedule_id":31,"server_id":13}
[2026-06-07 06:05:03] production.WARNING: Backup task already processing, skipping {"task_id":36,"schedule_id":33,"server_id":15}
[2026-06-07 06:20:22] production.WARNING: Backup task already processing, skipping {"task_id":37,"schedule_id":34,"server_id":16}
[2026-06-07 06:30:04] production.WARNING: Backup task already processing, skipping {"task_id":35,"schedule_id":32,"server_id":6

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions