Allow background task failure timer to be configurable

[phirestalker]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe. I shut down my Nextcloud server and database every night to back up. When it comes back up, background jobs that were scheduled are delayed for 12 hours because something failed.

Describe the solution you'd like I would like to be able to configure this wait time for my Nextcloud server.

Describe alternatives you've considered Since I use docker, the only way I can shut down the server is with the docker commands, so I am not sure there is an alternative.

Additional context

[SystemKeeper]

Try to adjust the maintenance window for background jobs: https://docs.nextcloud.com/server/latest/admin_manual/configuration_server/background_jobs_configuration.html#parameters

[phirestalker]

Thank you, but that seems to do the opposite of what I would like. This would bunch up all the jobs into a small 4-hour window. I was able to prevent this issue from occurring by setting maintenance mode in my backup script before shutting down Nextcloud and the database server. This prevents background jobs from running and failing with a missing database server. I would consider this something that should still be configurable, but it is not a huge priority for me.

[grzleadams]

This would be pretty nice. We have Recognize jobs that run and randomly fail due to some transient LDAP connection failure, and then they get deferred for 12 hours (or longer), when an immediate re-run (via background-job:execute) makes them succeed. Having this be configurable would be great.