Current Behavior
hi, from what i was told, pyrodactyl is supposed to automatically delete the oldest backup if the backup limit is reached for a scheduled backup. for example, my minecraft server shuts down at 12:55 AM, then a backup occurs at 1:00 AM, then the server starts up fine
the issue here is that if you look at this image

my scheduled backups has hit way over the 20 limit, and has not deleted any of the oldest ones
Expected Behavior
the expected behavior is for when pyrodactyl goes to make a scheduled backup, it will see if the limit is hit, so for example, if we are currently at 20 backups out of a 20 maximum, delete the oldest backup that isnt locked, then once its at 19 out of 20, create the backup
Steps to Reproduce
- make a pyrodactyl server of any kind
- make a schedule for a backup to be created on whatever basis, just repeating
- set a limit, eg 5 backups maximum or 20
- wait until scheduled backups occur
- watch as scheduled backups slowly get close to the limit you defined, then continue to make backups, even after the limit has been reached, which in my case, is how i have 77 of 20 backups
Panel Version
v5.0.5
Panel Installation Type
Daemon Version
v1.3.0
Daemon Installation Type
Games and/or Eggs Affected
Minecraft (Neoforge), Minecraft (Fabric)
Docker Image
ghcr.io/pterodactyl/yolks:java_21
Error Logs
https://ptero.co/lRcNEr
Second command did not work.
kade@pyrodactyl:/var/www$ tail -n 150 /var/www/pterodactyl/storage/logs/laravel-$(date +%F).log | nc pteropaste.com 99
tail: cannot open '/var/www/pterodactyl/storage/logs/laravel-2026-05-14.log' for reading: No such file or directory
no content received
kade@pyrodactyl:/var/www$
Is there an existing issue for this?
Current Behavior
hi, from what i was told, pyrodactyl is supposed to automatically delete the oldest backup if the backup limit is reached for a scheduled backup. for example, my minecraft server shuts down at 12:55 AM, then a backup occurs at 1:00 AM, then the server starts up fine

the issue here is that if you look at this image
my scheduled backups has hit way over the 20 limit, and has not deleted any of the oldest ones
Expected Behavior
the expected behavior is for when pyrodactyl goes to make a scheduled backup, it will see if the limit is hit, so for example, if we are currently at 20 backups out of a 20 maximum, delete the oldest backup that isnt locked, then once its at 19 out of 20, create the backup
Steps to Reproduce
Panel Version
v5.0.5
Panel Installation Type
Daemon Version
v1.3.0
Daemon Installation Type
Games and/or Eggs Affected
Minecraft (Neoforge), Minecraft (Fabric)
Docker Image
ghcr.io/pterodactyl/yolks:java_21
Error Logs
Is there an existing issue for this?