Schedule / Next Backup should show schedule suspension after error

[tvogel]

The problem

When I looked into Vorta today, I was a bit alarmed by the combination of an error message "Connection closed by remote host. Is borg working on the server?" from the last backup attempt in combination with "Next backup: None scheduled" (or similar, forgot to take a screenshot). This left me believe that Vorta would stop working its schedule if it encountered an error.

Looking at the log however, I found that clearly, execution of the schedule was just suspended:

2025-01-21 11:28:54,973 - vorta.scheduler - DEBUG - Paused 1 until 2025-01-21 11:58:54

Restarting Vorta immediately triggered a new (successful) backup run.

Requested Solution

So, it would avoid some confusion (for newbie users like me) to show "Paused until 2025-01-21 11:58:54 due to error" under "Next backup".

[shawnyeager]

I'm seeing the same errors today and came looking to see if others were, too. Thanks for the tip.

[bjo81]

We also stumbled about upon this issue, vorta cannot reach borg without vpn here, after suspension it tried to run a job immediately, failed and showed "Next backup: None scheduled". Maybe a configurable period of delay after suspension would be also fine.

[Elryth]

I may be experiencing the same issue, I had a failed backup due to being unable to connect to the server and having fixed that issue and backed up manually Vorta is still saying no backup scheduled. This has persisted through system reboot. If this doesn't sound like the same issue I'll keep looking/open a new issue.