Outlook rules are one of the most useful features in Microsoft’s email client — they can automatically sort, flag, forward, and delete emails without you lifting a finger. But they are also surprisingly fragile. A small misconfiguration, a conflict between two rules, or a sync problem can silently break them with no error message whatsoever. If your Outlook rules have stopped working, you are not alone, and the good news is that most of the common causes have straightforward fixes. This guide walks through each one so you can get your rules running again.
\n\n\n\nCommon Reasons Outlook Rules Stop Working
\n\n\n\nBefore diving into fixes, it helps to understand why Outlook rules break in the first place. There are several distinct causes, and the right fix depends entirely on which one you are dealing with.
- \n
- Client-side vs server-side rules — some rules only run when Outlook is open on your computer; others run on the server 24/7. If Outlook is closed when an email arrives, client-side rules will not trigger. \n\n\n\n
- Rule order conflicts — Outlook processes rules from top to bottom. If an earlier rule has a “stop processing more rules” action, everything below it gets silently skipped. \n\n\n\n
- 256KB rule storage limit — Exchange and Microsoft 365 accounts cap the total size of your rules at 256KB. Once you hit that limit, new rules fail to save and existing ones can behave unpredictably. \n\n\n\n
- Rules accidentally disabled — the checkbox next to a rule in the Manage Rules & Alerts dialog can be unchecked without you realising it. \n\n\n\n
- Corrupted rules file — for IMAP and POP accounts, rules are stored in a local .rwz file that can become corrupted, especially after a crash or update. \n\n\n\n
- Exchange vs IMAP account differences — server-side rules are only available on Exchange and Microsoft 365 accounts. IMAP and POP accounts rely entirely on client-side processing, which means rules only work when the desktop app is running. \n
If you are also having trouble with emails not arriving at all, check out the guide on Outlook not receiving emails before troubleshooting your rules, as a delivery problem upstream can look like a rules failure.
\n\n\n\nFix 1 — Check Rules Are Actually Enabled
\n\n\n\nThe simplest explanation is often the right one. Rules can be disabled without any obvious indication, particularly after an Outlook update or account re-authentication.
\n\n\n\n- \n
- Open Outlook and click the Home tab in the ribbon. \n\n\n\n
- Click Rules, then select Manage Rules & Alerts. \n\n\n\n
- In the Rules and Alerts dialog, look at the checkbox to the left of each rule name. \n\n\n\n
- Make sure every rule you want active has its checkbox ticked. \n\n\n\n
- Click OK to save any changes. \n
It is also worth checking the top of the dialog to see whether rules are enabled for the account at all. There is an option to disable all rules for a specific account, which can be toggled accidentally.
\n\n\n\nFix 2 — Check Rule Order and Conflicts
\n\n\n\nOutlook processes rules strictly from top to bottom, and a single rule with a “stop processing more rules” action can block every rule that comes after it. This is one of the most common causes of rules appearing to work intermittently — some emails trigger the blocking rule, others do not, and the behaviour looks random.
To check and fix rule order, open Manage Rules & Alerts (Home > Rules > Manage Rules & Alerts). Review your rules from top to bottom and look for any rule that has “stop processing more rules” in its actions column. Consider whether that rule should really be blocking everything below it, or whether the stop action should be removed.
\n\n\n\nTo reorder rules, select a rule and use the Move Up and Move Down arrow buttons at the top of the dialog. More specific or important rules should generally sit higher in the list.
\n\n\n\nFix 3 — Run Rules Manually to Test
\n\n\n\nRunning a rule manually is the fastest way to confirm whether the rule logic itself is sound, or whether the problem is something else entirely such as a sync issue or a disabled rule.
\n\n\n\n- \n
- Go to Home > Rules > Run Rules Now. \n\n\n\n
- In the Run Rules Now dialog, tick the checkbox next to the rule you want to test. \n\n\n\n
- Select the folder to run the rule on (usually Inbox). \n\n\n\n
- Click Run Now. \n
If the rule works when run manually but does not trigger on incoming emails, the issue is likely a client-side vs server-side conflict (covered in Fix 5 below). If the rule does not work even manually, the rule conditions themselves are probably the problem — go back and edit the rule to double-check the criteria. For a refresher on building rules from scratch, see our guide on how to create rules and filters in Outlook.
\n\n\n\nFix 4 — You’ve Hit the Rules Storage Limit
\n\n\n\nExchange and Microsoft 365 accounts have a hard cap on how much space your rules can occupy — 256KB in total. It sounds like a lot, but if you have been accumulating rules over years, or if your rules reference long lists of sender addresses, you can hit this limit faster than you would expect.
\n\n\n\nWhen you are at or near the limit, Outlook often cannot save new rules, and existing rules may silently fail. You might also see an error message saying “One or more rules could not be uploaded to Exchange server and have been deactivated.”
\n\n\n\nThe fix is to open Manage Rules & Alerts and delete any rules you no longer need. Also look for rules with very long condition lists — simplifying them (for example, by using a shared domain condition instead of listing individual addresses) frees up storage quickly.
\n\n\n\nFix 5 — Client-Side vs Server-Side Rules
\n\n\n\nThis distinction catches a lot of people out. In Outlook, some rules run on the mail server (so they process emails 24 hours a day, even when Outlook is closed), while others run locally on your computer and only activate when Outlook is open and connected.
\n\n\n\nRules that use certain actions — such as playing a sound, displaying a desktop alert, or running a script — can only run client-side. Outlook labels these with “(client-only)” in the rules list. If you rely on a client-only rule to move important emails, you will miss messages whenever your machine is off or Outlook is not running.
\n\n\n\nTo convert a rule to server-side where possible, edit the rule and remove any client-only actions. Replace them with server-compatible alternatives — for example, replace “display a desktop alert” with “mark as important” or “move to folder.” Not all rules can be fully converted, but removing even one client-only action can push the rule to server-side processing.
\n\n\n\nFix 6 — Delete and Recreate the Corrupted Rules File (IMAP/POP Accounts)
\n\n\n\nFor IMAP and POP accounts, Outlook stores rules in a local file with a .rwz extension. This file can become corrupted after a crash, a failed update, or a profile repair — and when it does, rules start behaving erratically or stop working entirely.
\n\n\n\nThe rules file is typically located at:
\n\n\n\nC:\\Users\\[YourUsername]\\AppData\\Roaming\\Microsoft\\Outlook\\
- \n
- Close Outlook completely. \n\n\n\n
- Navigate to the folder above (you may need to show hidden files in File Explorer). \n\n\n\n
- Find the file named rules.rwz (or a file named after your email account with a .rwz extension). \n\n\n\n
- Rename it to rules.rwz.old — do not delete it yet, in case you need to roll back. \n\n\n\n
- Reopen Outlook. A fresh rules file will be created automatically. \n\n\n\n
- Recreate your rules manually via Manage Rules & Alerts. \n
Once your rules are working correctly, you can delete the .old file. If something went wrong and you need your old rules back, rename the .old file back to .rwz and restart Outlook.
\n\n\n\nFix 7 — Rules Not Working After a Migration or Account Change
\n\n\n\nIf your rules stopped working around the time you migrated to Microsoft 365, changed your email host, or had your account type switched from IMAP to Exchange, the rules themselves may have been orphaned. Rules created under one account type do not always transfer correctly to another, and they can appear in the list while silently failing to execute.
\n\n\n\nThe cleanest solution after any account migration is to delete all existing rules and recreate them from scratch under the new account. It is tedious, but it eliminates any compatibility issues carried over from the old configuration. Before you do, take a screenshot or make a note of your existing rules so you can recreate them accurately.
\n\n\n\nIf you are also noticing that emails are not appearing in the right folders after a migration, it is worth checking the broader Outlook not syncing emails guide, as sync problems and rules failures often occur together after an account change.
\n\n\n\nFrequently Asked Questions
\n\n\n\nWhy do my Outlook rules only work sometimes?
\n\n\n\nIntermittent rules are almost always caused by one of two things: a client-side rule that only fires when Outlook is open, or a rule order conflict where a “stop processing more rules” action on an earlier rule sometimes catches the email first. Check Fix 2 and Fix 5 above to address both scenarios.
\n\n\n\nCan rules filter emails from an entire domain rather than a specific address?
\n\n\n\nYes. When setting up a rule condition based on the sender, you can enter just the domain portion — for example, @example.com — and Outlook will match any email from that domain. This is also much more storage-efficient than listing dozens of individual addresses, which helps if you are approaching the 256KB rules limit.
\n\n\n\nDo Outlook rules work on shared mailboxes?
\n\n\n\nIt depends on how the shared mailbox is configured. If you have added a shared mailbox as a separate account in Outlook, you can create rules for it directly in Manage Rules & Alerts by switching the account in the dropdown at the top of the dialog. If it is mounted as an additional folder under your primary account, rules may need to be set up by the mailbox owner or an administrator via Outlook Web Access.
\n\n\n\nWhy does my rule move emails but not mark them as read?
\n\n\n\nThis is a rule order issue within a single rule’s actions. Outlook does not always execute multiple actions in the order you would expect, and in some configurations “move to folder” can terminate further action processing. The workaround is to split the behaviour into two separate rules: one to mark as read, and one to move. Place the mark-as-read rule first (higher in the list) and remove “stop processing more rules” from it so the move rule still fires.
\n\n
