Add option to disable scheduled tasks #4233

New issue

Open

opened 2026-02-20 13:17:48 -05:00 by deekerman · 3 comments

deekerman commented

2026-02-20 13:17:48 -05:00

Owner

Originally created by @omnibaer on GitHub (Jan 2, 2026).

Is there an existing issue for this?

I have searched the existing open and closed issues

Currently, folder rescans occur daily, and for users working on importing large libraries, this can cause huge problems as Lidarr is unavailable for any work during this time (most database/file operations fail during a rescan).

Describe the solution you'd like

Please add checkboxes to System -> Tasks to allow users to disable scheduled tasks. This would help users with extremely large libraries to perform manual matching and updates without triggering large operations like folder rescans every time they update metadata etc.

Recommend a red health flag be set any time any scheduled task is disabled to remind the user to re-enable them.

Describe alternatives you've considered

I've attempted to change scheduled task intervals directly via database operations, but these do not appear to persist and are overwritten when Lidarr is restarted.

Anything else?

Nothing else. Thanks!

Originally created by @omnibaer on GitHub (Jan 2, 2026). ### Is there an existing issue for this? - [x] I have searched the existing open and closed issues ### Is your feature request related to a problem? Please describe Currently, folder rescans occur daily, and for users working on importing large libraries, this can cause huge problems as Lidarr is unavailable for any work during this time (most database/file operations fail during a rescan). ### Describe the solution you'd like Please add checkboxes to System -> Tasks to allow users to disable scheduled tasks. This would help users with extremely large libraries to perform manual matching and updates without triggering large operations like folder rescans every time they update metadata etc. Recommend a red health flag be set any time any scheduled task is disabled to remind the user to re-enable them. ### Describe alternatives you've considered I've attempted to change scheduled task intervals directly via database operations, but these do not appear to persist and are overwritten when Lidarr is restarted. ### Anything else? Nothing else. Thanks!

deekerman added the

Type: Feature Request

Status: Needs Triage

labels

2026-02-20 13:17:48 -05:00

deekerman commented

2026-02-20 13:17:50 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Jan 3, 2026):

Just set Rescan Artist Folder after Refresh to After manual refresh which accomplishes the exact thing you want to do, but without disabling the metadata refreshes. But I recommend After manual refresh as disabling it fully would break the scan even if you manual refresh and scan them from the UI.

You can disable Watch Root Folders for file changes too, if you want to go 100% manual.

@mynameisbogdan commented on GitHub (Jan 3, 2026): Just set `Rescan Artist Folder after Refresh` to `After manual refresh` which accomplishes the exact thing you want to do, but without disabling the metadata refreshes. But I recommend `After manual refresh` as disabling it fully would break the scan even if you manual refresh and scan them from the UI. You can disable `Watch Root Folders for file changes` too, if you want to go 100% manual.

deekerman commented

2026-02-20 13:17:50 -05:00

Author

Owner

@azgnetov commented on GitHub (Jan 12, 2026):

Just set Rescan Artist Folder after Refresh to After manual refresh

Not working for me or Lidarr ignores this option. Try to edit DB with command update ScheduledTasks set Interval=10080 where Id IN (5,6);

@azgnetov commented on GitHub (Jan 12, 2026): > Just set `Rescan Artist Folder after Refresh` to `After manual refresh` Not working for me or Lidarr ignores this option. Try to edit DB with command `update ScheduledTasks set Interval=10080 where Id IN (5,6);`

deekerman commented

2026-02-20 13:17:50 -05:00

Author

Owner

@mynameisbogdan commented on GitHub (Jan 12, 2026):

It works just fine for me.

@mynameisbogdan commented on GitHub (Jan 12, 2026): It works just fine for me.