Try the example, then check the result.
Download the fictional material and follow the steps below. The video uses English illustrative diagrams; it does not present a live app recording. Product controls may vary by version.
Check the answer before applying the method to your own data. How we review guides ↗
Watch the complete lesson.
The video uses English illustrative diagrams; it does not present a live app recording. English captions. Product menus may differ in your account.
An inbox rule can appear broken for different reasons. Use the fictional three-case triage sheet and rule diagnosis checklist before editing a real mailbox. This lesson separates three causes: an off rule, an earlier rule that stops processing, and a classic client-only rule that new Outlook cannot run. The video uses labelled illustrative diagrams, not a live mailbox recording.
Start with the Outlook version
Microsoft says File at the top indicates classic Outlook for Windows. In new Outlook or Outlook on the web, open Settings > Mail > Rules. In classic Outlook for Windows, open File > Manage Rules & Alerts.
Inspect the exact rule and the account where the target message arrives. Compare its condition with the message you expect to match. A sender, subject or folder mismatch is a different diagnosis from an engine failure.
Case A: the rule exists but is off
In the practice sheet, Project Updates is disabled. Inspect the rule's enabled state. If the action is still desired, use its toggle and confirm it shows on. That state is a configuration check. It does not prove a future message will be moved.
Case B: an earlier rule stops processing
Outlook processes rules in an order. The fictional broad project rule is earlier than a specific Priority rule, matches the same incoming message, and has Stop processing more rules. Microsoft documents that this prevents later rules from acting on that message.
Compare the conditions and order of both rules. If the specific Priority action is the intended one, consider moving it earlier or changing the broad rule's stop action. Review what else the broad rule handles before editing it; a different message may rely on the current behavior.
| Fictional order | Rule | Why Priority appears idle |
|---|---|---|
| 1 | Broad project rule + Stop processing more rules | It matches and stops the chain |
| 2 | Priority rule | It is never reached for that message |
Swipe or scroll sideways to see every table column →
Case C: a rule did not survive a version change
A migrated classic Outlook rule may show “This rule can't be edited or viewed” in new Outlook or Outlook on the web. Microsoft says a client-side condition or action can cause this. Classic Outlook can run client-side rules; new Outlook and web only support server-side rules.
Do not assume the old rule works simply because its name appears. Recreate it with a condition and action that the new client supports, if possible. If the desired action is truly client-only, use the appropriate classic Outlook workflow. Do not delete the original until the replacement has been tested.
Verify with a new message
If you edited the rule's conditions or actions, save that edit; if you only switched it on, confirm its toggle shows On. Then use a new, fictional incoming message that actually matches the condition and observe its folder or action. An enabled or saved rule is not proof of routing, and an old message already in the inbox is a weak test of automatic processing. No email was sent while preparing this lesson; the practice answers are diagnoses, not observed delivery results.
The independent answer check explains the correct branch for each fictional case.
Common questions
Does enabling a rule fix every case? No. An earlier stop rule or unsupported client-only action can still prevent the expected result.
Why does the rule name appear in new Outlook if it cannot run? A migrated client-side rule can remain visible with a warning. Follow Microsoft's version-specific guidance to rebuild a supported rule or use classic Outlook.
Can I verify using an old inbox message? For an automatic incoming rule, use a new matching message and observe what happens. Some versions offer a separate manual Run rule command, but that is a different test.
Sources and verification
Microsoft's rule repair guide documents the version routes and migrated client-only rule limits. Its Stop processing more rules guide explains why a later rule can be skipped. The rules management guide covers rule editing. Reviewed 12 October 2026. The practice cases were checked against these sources; a live incoming-message result remains unverified.
Practice downloads.
The exercise files contain invented information. Save a local copy before editing.