Upkeep
Cleanup safety limits
Three limits stand between a mis-scoped rule and your library, and they come in two groups that do different jobs. This is what catches a rule that quietly starts matching your whole library, usually because a list or collection it depends on came back empty.
Per rule — a ceiling on how many titles one rule may delete in a single cleanup pass. Go over and everything the rule matched is still queued with its countdown, you get a message, and the rule then deletes at most this many per pass. The rest wait for the next pass.
| Setting | What it does |
|---|---|
| Most titles per run | An absolute cap on the titles one rule may delete per pass. 0 means no limit. |
| Most of the library per run | The same cap as a percentage of the library. 0 means no limit. |
Both of these apply, and the stricter wins. The percentage never caps a run below 20 titles, so it cannot strangle a small library into never cleaning anything. Neither stops a run: what goes over is deferred to the next pass.
Across all rules — a cap on what actually gets removed, not queued.
| Setting | What it does |
|---|---|
| Most titles deleted per cleanup pass | How many titles may be removed in a single cleanup run, counting every rule together. 0 means no limit. |
It works the same way as the two above, but across every rule together. It does not stop the run. It deletes up to the cap and the rest stay in Leaving Soon for the next run. So a long act after countdown can hold a big queue without ever tripping it, and a mass deletion still cannot all happen at once.
Turning all three off is possible, and the Cleanup Rules page prints a red warning when you do, because that is the configuration in which a rule with a mistake in it runs to completion.