-
Notifications
You must be signed in to change notification settings - Fork 0
FAQ and Troubleshooting
No. Nudgarr sits alongside them and tells them what to search via their existing APIs. It does not manage your library, rename files, or handle downloads — that is still entirely handled by your arr apps and download client.
No. Each sweep nudges up to the configured Max per Run cap per pipeline, and items searched recently are skipped due to the cooldown. By default, each run nudges at most 1 Cutoff Unmet movie and 1 Cutoff Unmet episode per instance, 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. 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, excluded, or the Cutoff Unmet pipeline is toggled off. Check the Sweep tab stats for the relevant counts.
Nudgarr could not reach the instance during the last sweep. Common causes:
- The URL is wrong or contains a trailing path
- 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
The URL should be the base URL only — e.g. http://192.168.1.10:7878 with no trailing slash or path.
Overrides only take effect once you Apply them on each instance card in the Overrides tab.
Disabled instances are skipped in sweeps. Check the toggle state in the Instances tab and save again if needed.
The defaults are intentionally conservative. Increase Max per Run in the Settings tab to search more per sweep.
Nudgarr can only trigger the search — whether a result is found and grabbed depends on your indexers, quality profiles, and download client. Check the arr app's search logs for the relevant titles.
Verify that Cooldown (Hours) is set to a non-zero value in Settings. The default is 48 hours.
Check the Cutoff Unmet toggles in the Settings tab. There are separate toggles for Radarr and Sonarr. If either is off, that app's Cutoff Unmet pipeline is disabled entirely regardless of Max per Run.
The import check runs on its own independent timer (default: every 120 minutes). It may not have fired yet. You can trigger an immediate check from the Imports tab.
This means the same item has been imported more than once — an upgrade from a lower quality to a higher quality after the initial grab.
The most common cause is that cutoffFormatScore is set to 0 (or not configured) on your Sonarr quality profiles. If there is no score cutoff defined, every episode passes the gap check and nothing is indexed. Open Sonarr, go to Settings > Profiles, and set a non-zero custom format score cutoff on the profiles you want covered.
Another common cause is that all your series have a tag that matches an excluded tag in the Nudgarr Filters tab. Check your Sonarr instance filters — if a tag applied to all your series is in the excluded list, every series will be filtered before the sync can index anything.
This was a known bug fixed in v4.2.0. After a reset the index is empty so the status route previously returned no instances. Upgrade to the latest build to get progress rings visible from the start of the first scan.
This was a known bug fixed in v4.2.0. The button was calling a function that was never defined. Upgrade to the latest build.
Yes — back up /config/nudgarr.db (SQLite database) and /config/nudgarr-config.json. These two files contain everything.
If the container cannot parse the config file on startup, it falls back to defaults. Check the container logs for validation errors. The original file is left in place — you can inspect and correct it manually.
Deleting an instance removes it from sweeps and health checks but does not remove its historical data. Use Clear History and Clear Imports in the Advanced tab Danger Zone for a clean slate.
Expected on a fresh install or after Reset Intel. The score waits until 25 confirmed imports or 50 completed sweep runs have accumulated before calculating. All other Intel cards still display data during this period.
Intel data is stored in a protected aggregate that is not touched by Clear History or Clear Imports. If the numbers look unexpected after a clear, the Intel aggregate still holds the accumulated data from before the clear. This is correct behaviour. The live tables and the Intel aggregate will be out of sync for metrics that compare both — this rebalances over time.
For a fully clean slate, use Reset Intel (Intel tab) after clearing history and imports.
Both auto-exclusion thresholds are set to 0. Enable auto-exclusion thresholds in the Advanced tab to surface stuck items.
Check that at least one day of the week is selected and that the TZ environment variable is set correctly. The hint line below the time inputs in Settings will confirm the window is being interpreted as expected.
No. Run Now always fires immediately regardless of the maintenance window.
Auto-exclusion runs inside the import check loop, not during the sweep. A title will not be evaluated until the import check interval elapses after the sweep that pushed it over the threshold. To keep auto-exclusion responsive, set your import check interval equal to or shorter than your cron schedule.
This is a timing edge case — the title was grabbed after the last import check but before the current one ran, so the import was not yet confirmed when auto-exclusion evaluated it. To recover: find the title in the History tab Exclusions view and click Remove. The search count resets to 0 automatically.
On the History tab, click Clear Exclusions and select Clear Auto. A confirmation dialog appears before the action runs.
Try a hard refresh (Ctrl+Shift+R / Cmd+Shift+R). If still broken, check the container logs for startup errors.
Upgrade to v3.2.0 first, then to v4.0.0. Direct upgrades from pre-v3.2.0 installs are not supported.