Repository navigation
docs: correct when the log writes a skipped row - #802
Merged
Merged
Conversation
The skip-reasons page claimed every evaluated item gets a skipped row. Throttling, the context-mode drops, and the two cycle-level info rows all contradict that, as did the same page further down. Also states the Radarr 5.6.0 floor: the wanted endpoints Houndarr reads did not exist before then. Closes #801
This was referenced Sep 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #801
Four pages made claims the code does not support.
skip-reasons.mdopened by promising every evaluated item gets anaction=skippedrow. Eight reasons are throttled to one row per item per day,season/artist/author mode drops a row a sibling already accounted for, and the
two cycle-level reasons in its own table are written as
info. The page thencontradicted the opening twice further down. The table now marks those two rows
as info scope and says which action to filter on.
The deduplication section described the key as
(instance, item, reason). It is(instance, item, pass, reason bucket), and bothtag filterreasons share onebucket, so an item that fails the include filter and later the exclude filter
logs only the first.
compatibility.mdsaid any build exposing the v3 API should work. Houndarrreads Radarr's
/api/v3/wanted/missingand/api/v3/wanted/cutoff, whichRadarr added in 5.6.0; an older build connects and then returns nothing for both
passes.
search-order.mdclaimed chronological lets you predict which items come upnext, immediately above the sentence saying within-day order is arbitrary.
Docs only, no behaviour change.
Checklist
type:andpriority:labels