State the recurring requirement precisely
A recurring rule should express more than the title of a programme. Decide whether you want one channel, all relevant channels, new episodes or a particular recurring time slot. Write the requirement in ordinary language before selecting a recording type in NextPVR.
Use programmes you may record and check the actual guide data available to your server. The official documentation lists several recurrence choices and notes metadata requirements. A label such as new episode is only useful when the input guide can support the distinction; the scheduler does not independently verify broadcast history for you.
Choose a scope you can inspect
Start with the narrowest documented rule that meets the need. Compare the documented boundaries in the table with the actual requirement. A time-slot choice is not a promise to follow arbitrary future rescheduling. Channel-specific and all-channel choices also have materially different consequences. Review the installed interface and current help before relying on a label alone.
For an authored example, imagine a weekly permitted training broadcast with a repeat later in the week. Decide whether the priority is the first showing, any edition or only guide-marked new material. Those are different requirements. Do not add multiple overlapping rules merely because you are uncertain which one matches; overlapping schedules make the resulting pending list harder to explain.
| Documented web choice | Selection boundary |
|---|---|
| Record Once | Selected event only |
| NEW Episodes | New marking in the channel guide data |
| All Episodes | All episodes on that channel |
| All Episodes, All Channels | All channels at any time |
| Daily / Weekly timeslot | Relevant recurrence within one hour of the selected start |
Review generated occurrences before relying on the rule
Inspect the recurring rule and the individual pending recordings it produces. Compare several upcoming events with the written requirement, including a repeat or near-match that should be excluded. A rule saved without an error is not proof that its future selections are correct.
Review conflicts and priority when more than one rule needs the same recording resources. NextPVR's schedule documentation distinguishes recurring priorities and a conflicts view. A higher-priority rule expresses a preference under contention; it does not create another tuner or guarantee that every lower-priority programme will find an alternative broadcast.
Keep cancellation and retention intentional
Before cancelling something, distinguish a single pending episode from the recurring rule. The documentation describes different cancellation scope, so inspect which view you are using. Preserve the rule details before a substantial edit and review the new pending list afterward.
Also record the intended retention policy and available recording storage where relevant. A rule that schedules the right material still needs a plan for keeping or removing its files. Recheck representative occurrences after a guide-source change, schedule change or major server update. No recurring jobs were created or tested for this guide; completion means the locally generated occurrences match an explainable policy and its known metadata limits.
Questions answered
Can I assume a new-episodes rule independently knows every repeat?
No. Review the guide metadata and the generated occurrences; the documented behaviour depends on the available programme information.
Does cancelling one episode always remove its recurring rule?
No. Cancellation scope depends on the view and action. Inspect the recurring rule separately.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.