|
Is there a limit on how many items will be requested by Houndarr from the Arrs at each cycle? In my case ,Houndarr has reached a state where each cycle for my Radarr instance, 80 MISSING media items are skipped due to valid reasons (e.g. cooldown), and none are searched. It seems that the list of MISSING media items is alphabetical, and each cycle the same "stale" 80 items are evaluated and eventually skipped, so none of the remaining MISSING items in Radarr are triggered for searching. There is similar behaviour for CUTOFF media items, although in this case the max number is 40 items per cycle. I can't find any setting for controlling the quantity of items per cycle. If this can't easily be changed , perhaps Houndarr could randomise the MISSING and CUTOFF items from the Arrs - which would ensure that each cycle there are some "fresh" items being evaluated |
Replies: 1 comment
|
Good catch. You were right on both counts: the missing and cutoff passes always started from page 1, and with the 5-page-per-pass cap, items further down the list were never reached once the first pages were all on cooldown. This is fixed in #294. Each pass now remembers which API page it stopped at and starts from there on the next cycle. When it pages past the end of available data, it wraps back to page 1 within the same cycle so nothing is permanently skipped. The upgrade pass already had offset-based rotation for this reason. The missing and cutoff passes just lacked the same treatment. The fix also ensures that when the batch fills partway through a page, the offset stays on that page so the remaining items get evaluated next time. This will be included in the next release. |
Good catch. You were right on both counts: the missing and cutoff passes always started from page 1, and with the 5-page-per-pass cap, items further down the list were never reached once the first pages were all on cooldown.
This is fixed in #294. Each pass now remembers which API page it stopped at and starts from there on the next cycle. When it pages past the end of available data, it wraps back to page 1 within the same cycle so nothing is permanently skipped.
The upgrade pass already had offset-based rotation for this reason. The missing and cutoff passes just lacked the same treatment. The fix also ensures that when the batch fills partway through a page, the offset stays on that pa…