yolo/arr
3
0
Fork 0
Code Issues 12 Pull Requests Actions Packages Projects Releases Wiki Activity

Reconcile episodes that vanish or renumber upstream #122

New Issue
Closed
opened 2026-08-23 15:55:56 +01:00 by naps62-yolo · 0 comments
naps62-yolo commented 2026-08-23 15:55:56 +01:00
Owner
Copy Link
Copy Source

Depends on: #121

TMDB deletes and renumbers episodes. #121 deliberately leaves them alone, so a
removed episode stays wanted forever and holds its series at incomplete.

  • An episode that vanished upstream and has no file is deleted, cascading
    through episode_releases.
  • An episode that vanished upstream and has a file is never deleted. Flag it
    and surface it as a conflict for the operator to resolve. media_files.path
    is unique and the owner is polymorphic, so deleting the row would orphan a
    real file and block re-importing that path — the same trap
    crates/arr-api/src/movies.rs:366 documents on the movie side.
  • Renumbering is the same two cases seen from the other end: the old number
    vanishes and a new one appears. Do not try to match them up. A renumber that
    strands a file shows as a conflict, which is the honest answer.

Nothing here deletes anything from disk.

Depends on: #121 TMDB deletes and renumbers episodes. #121 deliberately leaves them alone, so a removed episode stays wanted forever and holds its series at `incomplete`. - An episode that vanished upstream and has no file is deleted, cascading through `episode_releases`. - An episode that vanished upstream and **has** a file is never deleted. Flag it and surface it as a conflict for the operator to resolve. `media_files.path` is unique and the owner is polymorphic, so deleting the row would orphan a real file and block re-importing that path — the same trap `crates/arr-api/src/movies.rs:366` documents on the movie side. - Renumbering is the same two cases seen from the other end: the old number vanishes and a new one appears. Do not try to match them up. A renumber that strands a file shows as a conflict, which is the honest answer. Nothing here deletes anything from disk.
naps62-yolo added the difficulty/moderatearea/daemonphase/6-tvtype/feature labels 2026-08-23 15:55:56 +01:00
naps62-yolo added this to the TV tracking milestone 2026-08-23 15:58:35 +01:00
naps62-yolo added a new dependency 2026-08-23 16:36:55 +01:00
#121 Daily series metadata refresh
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
arr-api
 area/ci
CI and test harness
 area/compat
arr-compat
 area/core
arr-core
 area/daemon
arr-daemon
 area/db
arr-db
 area/dl
arr-dl
 area/indexer
arr-indexer
 area/infra
workspace and tooling
 area/meta
arr-meta
 area/parse
arr-parse
 area/probe
arr-probe
 area/subs
arr-subs crate: providers, extraction, translation, sync
 area/web
web/
 difficulty/easy
bounded, obvious approach, few files
 difficulty/hard
subtle correctness or cross-cutting
 difficulty/moderate
multiple files, judgement, an interface to design
 difficulty/trivial
one file, mechanical, no design decisions
 phase/1-skeleton
workspace, CI, config, database, empty API and SPA
 phase/2-logic
parsing and policy engine, pure, no network
 phase/3-sourcing
TMDB and Prowlarr, read-only
 phase/4-movies
movies end to end
 phase/5-ui
search, buckets, library views, queues
 phase/6-tv
seasons, episodes, tracking, derived status
 phase/7-people
owner tags and notifications
 phase/8-compat
Jellyseerr shim
 phase/9-subtitles
build order: subtitles, DESIGN.md §15
 type/bug
type/chore
type/feature
type/test
No labels area/daemon difficulty/moderate phase/6-tv type/feature
Milestone
No items
No Milestone TV tracking
Projects
Clear projects
No projects
Assignees
Clear assignees
hermes (Hermes (agent)) naps62 (Miguel Palhas) naps62-yolo (naps62-yolo (agent))
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Depends on
#121 Daily series metadata refresh
yolo/arr
Reference: yolo/arr#122