Condition code change with scale-out repos

[pj888888888888]

So we had an issue with one of our physical storage repos, and I put it in maint. mode in a scale-out repo.
The jobs are all failing now, simply because it cannot access the repo because its in maint. mode and cannot expire the backups.
Would it be possible to have this instead of being a failure, maybe just have it be a warning?
I view failures as a failure to backup data, not failure to expire old backups (thats just me though )

[foggy]

Hi Paul, currently retention is considered a part of the job, which defines the behavior you're seeing. This is something to think about, so let's consider this a feature request.

[pj888888888888]

Excellent!
I think it would be good if it were a warning instead, granted it would be good to know for storage consumption, but its flood the failed list right now, and its making it hard to find actual problems vs. a non-issue.