-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ and Troubleshooting
No. Nudgarr sits alongside them and triggers searches via their existing APIs. It does not manage your library, rename files, or handle downloads — that's still entirely handled by your arr apps and download client.
No. Each sweep searches up to the configured Max per Run cap, and items that were searched recently are skipped due to the cooldown. By default, each run searches at most 1 Cutoff Unmet movie and 1 Cutoff Unmet episode across all instances, with a 48-hour cooldown preventing the same item from being re-searched within that window.
Make sure Automatic Sweeps is toggled on in Settings. By default it is off — Nudgarr is configured for manual-only operation until you explicitly enable the scheduler. Once enabled, the first sweep fires at the next cron trigger, not immediately.
History writes happen during the sweep. If nothing appears, it is likely that all eligible items were filtered out — either on cooldown, already queued, or excluded. Check the Sweep tab stats for On Cooldown and Queued counts to see where items were filtered.
Nudgarr could not reach the instance during the last sweep. Common causes:
- The URL is wrong or contains a trailing path that shouldn't be there (e.g.
/radarrwhen the instance is at the root) - The API key is incorrect or has been rotated
- The arr app is down or unreachable from the Nudgarr container
- A network or firewall rule is blocking the connection
Check Settings → Instances, edit the affected instance, and verify the URL and API key. The URL should be the base URL only — e.g. http://192.168.1.10:7878 with no trailing slash or path.
You can, but it isn't useful — Nudgarr will process it twice per sweep, potentially searching the same items from two passes. Use multiple instances when you have genuinely separate arr installs (e.g. a main library and a 4K library).
Overrides only take effect once you Apply them on each instance. Open the Overrides tab on desktop or rotate to landscape on mobile, select the instance, set your values, and click Apply.
Disabled instances are skipped in sweeps and health checks. Check the toggle state in the Instances tab. If the toggle appears on but the instance should be disabled, try toggling it off and saving again.
The defaults are intentionally conservative (1 movie, 1 episode, 48-hour cooldown). This is safe for any indexer. Increase Max per Run in Settings to search more per sweep.
Nudgarr can only trigger the search — whether a result is found and grabbed depends on your indexers, Radarr/Sonarr's quality profiles, and your download client. If searches are being triggered but nothing downloads, the issue is upstream of Nudgarr. Check the arr app's search logs for the relevant titles.
If an item appears repeatedly in History with short gaps between searches, cooldown may not be working correctly. Verify that Cooldown (hours) is set to a non-zero value in Settings. The default is 48 hours.
Skip Queued is always on and requires no configuration. If a queued item appears to have been searched, check whether it was queued at the time of the sweep — items added to the queue after a sweep starts are not retroactively skipped.
The import check runs on its own independent timer (default: every 120 minutes). It may not have fired yet after installation. You can also check whether Nudgarr has had enough time to search items and for those items to be downloaded — the import check only records confirmed imports of previously searched items.
Turnaround is measured from first_searched_ts — the first time Nudgarr ever searched that item — to the confirmed import. If you imported an item a long time after Nudgarr first searched it (e.g. an item that sat waiting for a release), the turnaround will reflect that full duration.
This means the same item has been imported more than once — typically an upgrade from a lower quality to a higher quality after the initial grab. The counter increments on each confirmed import of the same item.
Yes — back up /config/nudgarr.db (SQLite database) and /config/nudgarr-config.json. These two files contain everything: settings, history, exclusions, stats, and app state.
If the container cannot parse the config file on startup, it falls back to defaults. Check the container logs (docker logs nudgarr) for validation errors. The original file is left in place — you can inspect it and correct any invalid values manually.
Stop the container, delete /config/nudgarr-config.json and /config/nudgarr.db, then restart. Nudgarr will re-run the first-run onboarding flow.
Deleting an instance removes it from sweeps and health checks but does not remove its historical data. Search history and confirmed imports are kept in the database. To remove the data, use Clear History and Clear Imports in the Advanced tab for a clean slate.
Auto-exclusion runs inside the import check loop, not during the sweep itself. This means a title will not be evaluated for auto-exclusion until the import check interval elapses after the sweep that pushed it over the threshold.
If your import check interval is longer than your cron schedule, a title could be searched multiple times across several sweeps before the import check fires and evaluates it. For example, with a cron every 60 minutes and an import check interval of 120 minutes, a title could accumulate two or more searches before auto-exclusion has a chance to run.
To keep auto-exclusion responsive, set your import check interval equal to or shorter than your cron schedule. With matching intervals, auto-exclusion will evaluate titles within one cron cycle of the threshold being reached. The import check interval is in Advanced → Import Check Interval (minutes).
This is a timing edge case. The auto-exclusion check runs at the end of the import check cycle and evaluates titles that have no confirmed import at that moment. If a title was grabbed and imported within the current import check window — i.e. it downloaded after the last import check but before the current one ran — the import will not yet be confirmed in the database when the auto-exclusion check fires. The title passes the "no confirmed import" condition and gets excluded.
This is not a bug. To recover: open the Exclusions tab (History → Excluded on mobile, or History tab with exclusions filter active on desktop), find the title, and click Remove. The search count resets to 0 automatically when removing an auto-excluded entry, so the title gets a clean slate and will not be immediately re-excluded.
Reducing the import check interval makes this window smaller and reduces the chance of it happening.
Open Advanced → Danger Zone and click Reset Auto-Exclusions. This removes all entries with source=auto. Manual exclusions are not affected. A confirmation dialog appears before the action runs.
This is expected behaviour. The What's New modal appears once after an upgrade when the version has changed. It can be dismissed and will not appear again until the next version.
Try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R). From v4.1.0 onwards, all static file URLs include a version query string (e.g. ui-core.js?v=4.1.0) so browsers automatically fetch fresh JS and CSS on upgrade without needing a manual cache clear. If you are upgrading from a version before v4.1.0, a one-time hard refresh may be needed.
If the UI is still broken after a hard refresh, check the container logs (docker logs nudgarr) for startup errors.
This migration ran automatically when upgrading to v3.1.0 or v3.2.0. If you are running v4.0.0 and arrived here from a pre-v3.1.0 install without going through v3.2.0 first, the migration code is no longer present — you will need to start fresh or restore from a backup. Upgrades from pre-v3.1.0 installs should go via v3.2.0 before upgrading to v4.0.0.