Wait for the right signals.
Then let the PC act.

When one condition is not enough

A low CPU reading can mean that a render is finished—or that it is merely waiting to write files. Quiet network traffic can mean a download is done—or that it has paused for a moment. Combining signals makes it less likely that an automatic action runs too early.

Auto Shutdown & Scheduler’s Custom Rule brings together two to four compatible monitor conditions. You choose the action and decide whether every condition must match, or whether any one of them is enough.

Understand AND and OR logic

The logic is simple, but the consequences are different:

1. AND: every selected condition must be true. This is safer when you need evidence that several kinds of activity have settled.
2. OR: any selected condition can start the action. This suits alternative stopping points, but it should be used carefully because the first matching condition wins.
3. Start small: combine two conditions first. Add more only when they improve the decision instead of making it harder to understand.

For example, an AND rule can wait until CPU usage is low and network traffic is quiet. That is more deliberate than treating either signal alone as proof that all work has finished.

Build a rule around your workflow

Good rules describe a specific, observable finish line. A few useful patterns:

1. Long transfer plus post-processing: wait for CPU and network activity to settle before sleeping or shutting down.
2. Creative work: use CPU monitoring alongside another compatible signal when a renderer has more than one active stage.
3. Multiple monitored tasks: use OR only when either condition genuinely means it is safe to take the same action.

Conditions must be compatible in the app. That guardrail prevents combinations that do not represent a meaningful, reliable automation.

Test before you trust it overnight

First enable the component monitors individually and observe their behavior. Learn what normal idle CPU, network, disk, or other activity looks like on your PC. Then create the Custom Rule with an action that is easy to recover from, such as Lock or Sleep, before relying on Shut Down.

Keep a pre-action warning enabled for disruptive actions. If a condition becomes true during an unexpected pause, the warning gives you a final chance to cancel and refine the rule.

Keep rules readable

Name the intent in your own words before building the automation: “shut down only after the transfer and processing are both calm.” If you cannot explain the rule in one sentence, it is probably too complex.

Review Custom Rules whenever your workflow changes. New background apps, different export settings, or a changed network connection can alter the signals that made an old rule dependable.