Skip to content

docs: correct when the log writes a skipped row - #802

Merged
av1155 merged 1 commit into
mainfrom
docs/correct-log-row-claims
Sep 18, 2026
Merged

av1155 merged 1 commit into
mainfrom
docs/correct-log-row-claims

Conversation

@av1155

@av1155 av1155 commented Sep 18, 2026

Copy link
Copy Markdown
Owner

Closes #801

Four pages made claims the code does not support.

skip-reasons.md opened by promising every evaluated item gets an
action=skipped row. 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 then
contradicted 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 both tag filter reasons share one
bucket, so an item that fails the include filter and later the exclude filter
logs only the first.

compatibility.md said any build exposing the v3 API should work. Houndarr
reads Radarr's /api/v3/wanted/missing and /api/v3/wanted/cutoff, which
Radarr added in 5.6.0; an older build connects and then returns nothing for both
passes.

search-order.md claimed chronological lets you predict which items come up
next, immediately above the sentence saying within-day order is arbitrary.

Docs only, no behaviour change.

Checklist

  • Linked issue has type: and priority: labels
  • Docs site builds
  • Tests added or updated (N/A, documentation only)

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
@av1155
av1155 merged commit 2a0bd77 into main Sep 18, 2026
19 checks passed
@av1155
av1155 deleted the docs/correct-log-row-claims branch September 18, 2026 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: correct when the log writes a skipped row

1 participant