The Complete Guide to Continue Watching Hygiene
A practical operating system for keeping Continue Watching focused on titles you genuinely intend to resume.
In short: A useful Continue Watching row contains titles you genuinely plan to resume, with the correct profile, version, episode, and progress. Classify each entry as active, sampled, completed, paused, or unresolved. Fix identity or sync questions before removing anything, and run a short weekly review rather than waiting for the row to become unmanageable.
Continue Watching is a decision surface, not an archive. Its job is to reduce the distance between “I want to carry on” and playback. Hygiene means keeping that promise accurate without treating every unfamiliar card as clutter.
Define what belongs in the row
Use intent rather than age alone. An older title can remain useful when you deliberately paused it, while yesterday’s two-minute sample may already be noise.
| State | Evidence | Appropriate action |
|---|---|---|
| Active | You expect to resume soon | Keep and prioritise |
| Sampled | You only tested or previewed it | Decide keep or clear |
| Completed | You reached your intended ending | Verify completion state |
| Paused | You chose a later return point | Keep with a review date |
| Unresolved | Identity, version, episode, or progress is unclear | Investigate before changing |
The matrix prevents two common errors: deleting a legitimate pause and preserving a sample merely because it is recent. Triage sampled titles deliberately instead of applying one rule to every short session.
Check context before changing state
Read the visible profile or viewer, exact title, media type, episode, progress indicator, and any version clues. A matching poster is not enough when two editions or episodes look alike. DCMI metadata terms distinguish a work’s identifier, relation, format, and language; those distinctions are useful whenever a row contains similar cards.
Norva’s public feature description says progress and preferences can stay with the same account across supported devices. That makes context especially important: a change observed on one screen may reflect another supported screen, a different profile, or a different version. The exact behavior in the current build still needs verification before publication.
Use a safe review loop
Process one item at a time:
- Identify it. Confirm title, series or film level, episode where relevant, and visible version clues.
- Name the viewer. Verify the active profile rather than inferring it from the screen location.
- Read progress. Record the displayed point without deciding yet whether it is correct.
- State intent. Choose resume soon, pause, completed, sampled, or investigate.
- Take one reversible action. Avoid bulk changes until scope is proven.
- Reopen the row. Confirm the intended entry changed and neighbouring entries did not.
When the list is long, prioritise genuinely active items before working on edge cases. The goal is a useful top section, not instant perfection.
Diagnose rather than guess
A surprising row can have several explanations. Progress may have been recorded under another profile, playback may have used another version, an episode transition may need review, or another device may not yet show the same state. These are diagnostic possibilities, not claims that a particular cause applies.
Capture a minimal evidence set: date and local time, device category, active profile label, title and episode text, displayed progress, expected result, and the steps just taken. Never include passwords, source credentials, or unnecessary personal viewing detail. The support-ready documentation workflow explains how to make this record useful.
Build a sustainable cadence
A weekly review is enough for many viewers because it catches samples and completed entries while intent is still memorable. Add an event-triggered review after a profile switch, source change, long offline period, or version change. Use the weekly resume-row routine as a ten-minute structure, not as a quota to remove items.
For a final release gate, the Continue Watching checklist verifies identity, viewer, progress, intent, cross-screen state, and recovery before a larger cleanup.
Original evidence: the five-state decision matrix
Copy the table above into a private note and test it on five non-sensitive entries. For each one, record only state, confidence, and next action. If two reviewers assign different states, the missing evidence becomes visible: perhaps intent was never stated, the version is ambiguous, or profile scope is unknown.
The matrix does not prove how software recorded progress. It provides a reproducible way to avoid destructive guesses and to separate curation decisions from technical investigation.
Common mistakes and limitations
- Treating every short progress marker as a sample.
- Assuming the visible account proves the active profile.
- Removing duplicate-looking cards before comparing versions.
- Interpreting temporary cross-screen differences as permanent loss.
- Recording sensitive viewing or account data in a cleanup sheet.
- Expecting hygiene to repair source metadata or unavailable media.
Available titles, languages, subtitles, and offline behavior depend on the compatible source, media, device, and associated rights. Hygiene can clarify state; it cannot create missing availability.
Frequently asked questions
Should Continue Watching contain only recent titles?
No. Current intention is more useful than a universal age limit. Keep a deliberate long pause if it still has a return plan.
Is a short progress marker always safe to clear?
No. It may represent a genuine start, a replay, or an ambiguous version. Confirm identity and intent first.
How many items should the row contain?
There is no universal ideal. It is healthy when the viewer can find active items quickly and explain the purpose of uncertain entries.