Overview
Module: Sonarr & Radarr
Activity type: Lesson (Orient → Recall → Learn → Explain → Reflect)
Learning objective: Differentiate monitored state from missing, available, downloaded, and cutoff-unmet states
Bloom level: Understand / Apply
Last reviewed: 2025-03-08
Learning objective
Differentiate monitored state from missing, available, downloaded, and cutoff-unmet states
Why this matters
Teach administrators how Sonarr monitoring, episode state, release availability, quality cutoffs, and search behavior interact. The lesson emphasizes predicting Sonarr's decisions before changing a production library.
Learn
Complete the module reading first:
Feynman teach-back: required
prompt
Explain monitoring to a family member who thinks selecting a show means every episode will immediately download.
model_explanation
Monitoring tells Sonarr which episodes it is allowed to care about. Sonarr still waits until an episode is considered available, looks for releases through an indexer, rejects releases that do not meet the rules, and asks a download client to transfer an accepted one. An old missing episode may also need a deliberate historical search because the normal feed mainly evaluates newly posted releases. A file can already exist and still be monitored for an upgrade if it has not reached the quality cutoff.
self_check
Your explanation should separately mention intent, availability, searching, acceptance rules, downloading, and quality upgrades. If monitored and downloaded are used as synonyms, revise the explanation.
Answers save in this browser (localStorage). Completing all five fields is part of the mastery unlock.
Reflection
- What did I learn?
- What did I struggle with?
- How does this connect to earlier classes?