[Bug]: Scheduled backup remains stuck in "pending" status after a manual restore completes

[edmc73]

DBackup Version

v2.3.3

Installation Method

Docker (docker-compose)

Bug Description

While a manual database restore process was running, a scheduled backup task triggered as planned. Since the restore task was active, the backup task was naturally placed into a "pending" queue.

However, once the restore operation successfully finished, the backup task did not resume or start. It remains permanently stuck in the Pending status and never executes, blocking the queue.

Steps to Reproduce

Start a manual database restore process.

Wait for a scheduled backup task to trigger (or force trigger one) while the restore is still active.

Observe that the backup task status changes to "Pending" (expected behavior).

Wait for the restore process to finish.

Notice that the backup task remains stuck in "Pending" indefinitely instead of starting.

Expected Behavior

The pending backup task should automatically start processing as soon as the active restore job releases the lock/finishes.

Logs / Error Output

Screenshots

No response

Environment

No response

[Skyfay]

Hey @edmc73

Thanks for reporting.

I'll take a look soon. In the meantime you should be able to restart the dbackup container and the task should be set to failed.
Hope this helps :)

[edmc73]

Yes, restart the dbackup container set the task in failed.
Thanks :)

[Skyfay]

Hey @edmc73

This works now in the latest version v2.4.0

Thanks for reporting this :)