1
00:00:00,080 --> 00:00:03,970
If an Outlook rule seems to do nothing, do not delete

2
00:00:03,970 --> 00:00:05,738
it and start over yet.

3
00:00:05,738 --> 00:00:09,628
Three common explanations are an off switch, an earlier rule that

4
00:00:09,628 --> 00:00:13,871
stops processing, or a classic Outlook rule that new Outlook cannot run.

5
00:00:13,871 --> 00:00:17,408
We will diagnose three fictional cases, then distinguish a saved

6
00:00:17,408 --> 00:00:20,944
configuration from a rule that actually handled a new message.

7
00:00:21,544 --> 00:00:26,242
Microsoft says that seeing File at the top means classic Outlook for Windows.

8
00:00:26,242 --> 00:00:30,940
In new Outlook or Outlook on the web, open Settings, Mail, then Rules.

9
00:00:30,940 --> 00:00:34,192
In classic Outlook, use File, Manage Rules and Alerts.

10
00:00:34,192 --> 00:00:38,167
Keep those routes separate because classic supports some rules that run

11
00:00:38,167 --> 00:00:43,587
only on your computer; new Outlook and the web do not run client-side rules.

12
00:00:44,187 --> 00:00:48,889
In the fictional Project Updates case, the rule is present but switched off.

13
00:00:48,889 --> 00:00:53,228
Open the Rules list and inspect its enabled state before changing conditions.

14
00:00:53,228 --> 00:00:57,207
If the behavior is still desired, use its toggle and confirm

15
00:00:57,207 --> 00:00:58,653
that it shows on.

16
00:00:58,653 --> 00:01:01,908
That confirms the setting, not the final delivery outcome.

17
00:01:01,908 --> 00:01:05,886
A new incoming test message is needed to prove that matching

18
00:01:05,886 --> 00:01:07,333
mail follows the rule.

19
00:01:07,933 --> 00:01:13,453
In the second fictional case, a broad rule appears above a specific Priority rule.

20
00:01:13,453 --> 00:01:18,974
The earlier rule also has Stop processing more rules and matches the same message.

21
00:01:18,974 --> 00:01:23,311
Microsoft documents that this action prevents later matching rules from running.

22
00:01:23,311 --> 00:01:25,677
Compare both rules' conditions and order.

23
00:01:25,677 --> 00:01:30,015
If the specific behavior is intended, move that rule earlier or

24
00:01:30,015 --> 00:01:31,987
revise the stop action thoughtfully.

25
00:01:32,587 --> 00:01:36,868
A different clue is the warning, This rule can't be edited

26
00:01:36,868 --> 00:01:40,080
or viewed, after moving from classic to new Outlook.

27
00:01:40,080 --> 00:01:42,934
Microsoft says client-side actions can cause this.

28
00:01:42,934 --> 00:01:47,573
New Outlook cannot run those actions just because the old rule name appears.

29
00:01:47,573 --> 00:01:51,498
Recreate the rule only with actions supported in new Outlook, or

30
00:01:51,498 --> 00:01:55,423
use classic Outlook when the action truly requires the desktop client.

31
00:01:56,023 --> 00:01:58,345
The downloadable table has three cases.

32
00:01:58,345 --> 00:02:02,987
Mark A as disabled, B as a rule-order conflict with Stop

33
00:02:02,987 --> 00:02:06,856
processing, and C as an unsupported migrated client-side rule.

34
00:02:06,856 --> 00:02:11,112
Then decide whether you are authorized to change the real mailbox

35
00:02:11,112 --> 00:02:13,820
and what the intended behavior should be.

36
00:02:13,820 --> 00:02:18,850
Preserve the original rule until you know which condition or action needs correction.

37
00:02:19,450 --> 00:02:24,463
After an authorized change, an enabled or saved rule is only the first checkpoint.

38
00:02:24,463 --> 00:02:28,402
Use a new fictional incoming message that matches the condition, then

39
00:02:28,402 --> 00:02:31,625
observe where Outlook puts it or which action occurs.

40
00:02:31,625 --> 00:02:36,639
Do not rely on an old message already in the inbox as the test.

41
00:02:36,639 --> 00:02:40,578
No message was sent for this video, so its examples show

42
00:02:40,578 --> 00:02:44,517
documented settings and expected checks, not a demonstrated live delivery result.