Repository navigation
[Enhancement]: Add Smart Job Retry Setting #170
Description
Current Behavior
Currently, when a backup job fails at any point, it needs to be run manually or wait for the next scheduled run.
Proposed Improvement
Add a retry setting to the backup jobs (ideally with the option to set templates and defaults) that would allow X number of retries when a job is failing.
The retry should be smart, meaning that if the job fails to upload the backup to the destination, it should only try to upload it again, not start over (this will save time and resources for large backups).
Motivation
Most backups are automated and when they fail for any reason, the automation is no longer there until the next scheduled run which can easily lead to missing backups if not actioned manually in time.
Area
Backup / Restore
Additional Context
No response
Activity
Skyfay commentedon Sep 27, 2026
Hey @KrzysztofKiser
Thank you for creating this issue. I think it definitely makes sense for scenarios where, for example, a storage provider is temporarily unavailable. However, based on my experience, I would say that often when something doesn't work, it's something that a retry can't fix. You usually have to do that by hand.
But I'll add it to the list for now, and I'll take another look at it later :)
KrzysztofKiser commentedon Sep 27, 2026
Thank you! ❤️
It's generally not a huge problem when noticed in time, but for large backups that take hours to complete, it makes no sense to start from scratch when the archive is already there, it just needs to try to upload it again.