Default cronjobs are incorrect. about overseerr HOT 3 OPEN

"These default values are not encoded in the UI, and cannot be reset to defaults without manually editing settings.json or reinstalling."
Thats not entirely true, you can always modify them using the REST API.

from overseerr.

"For each cronjob setting, it seems that the "default" install settings which are impossible to reset to in the UI; this applies to all jobs. Additionally dropdowns are seemingly very restricted."

The point of the bug was that it was not addressable in the UI; regardless of manually editing settings.json or using the API.

from overseerr.

We opted to not add the ability to specify a cron string in the UI because that wouldn't be really user friendly, especially considering that there's a good amount of people that use Overseerr who don't know what a cron string is. And if someone wants to get fancy with it, they can put their cron string directly in the settings file or use the OpenAPI docs viewer to set it. So I don't think we'd add that.

Setting the job back to it's default schedule would be a feature request, and should be fairly easy if you'd want to make a pull request.

from overseerr.