How to Fix Outlook Rules That Do Not Run When Outlook Is Closed

Many people create an Outlook rule, test it while Outlook is open, and watch it work perfectly. Then they close Outlook for the night, and by morning the rule seems to have done nothing at all. New mail is sitting unfiled, unflagged, or unforwaded, even though the same rule runs happily during the day.

This problem usually comes down to one key distinction that Outlook does not make obvious: some rules run on the mail server, and others can only run on your computer. Understanding which type you created explains the whole puzzle. This guide shows you how to tell server rules from client-only rules, how to rebuild a rule so it keeps working when Outlook is closed, and when that simply is not possible.

Quick Answer

A rule only runs when Outlook is closed if it is a server-side rule stored on Microsoft Exchange or Microsoft 365, using conditions and actions the server can handle alone. If your rule is marked client-only, or uses actions such as moving mail to a local folder, playing a sound, or running a script, it needs Outlook open and will pause until you start it again. Recreate the rule in Outlook on the web or remove the client-only parts to make it run on the server.

Server Rules and Client-Only Rules Explained

When your mailbox lives on Exchange or Microsoft 365, your rules can live in two places. Server-side rules are stored with your mailbox on the server. The server applies them to new mail as it arrives, day and night, whether your computer is on, off, or on holiday with you.

Client-only rules live in Outlook on your computer. Outlook itself has to process them, so they only run while the program is open and signed in to your account. Outlook usually warns you about this when you save such a rule, with a message saying the rule is a client-only rule and will run only when Outlook is running. That warning is easy to click past during setup, and it is the root of most complaints like this one.

Actions That Force a Rule to Be Client-Only

Certain conditions and actions cannot be done by the server, because they involve your local computer or local files. Common examples include:

• Moving or copying messages to a folder in a local PST file or an On My Computer folder.
• Playing a sound, showing a desktop alert in a specific local way, or displaying a custom notification message.
• Running a script or a custom action installed on your computer.
• Using conditions based on something only your computer knows, such as a local category setup in some configurations or a specific form stored locally.

By contrast, the server handles core mail actions well: moving a message to another folder inside the same mailbox, deleting it, marking it as read, flagging it, and forwarding it where policy allows. Rules using only actions like these can usually live on the server.

How to Check Whether Your Rule Is Server-Side

1. Open Outlook on the web for your work account, or open the Rules settings in Outlook and look at the rule list.
2. In Outlook on the web, go to Settings, then Mail, then Rules. Rules shown here are server rules, because the web version only manages rules stored on the server.
3. In classic Outlook for Windows, open File, then Manage Rules and Alerts, and read the description under each rule. Client-only rules are often marked in the list or described with actions that reference this computer.
4. Select your problem rule and read its full conditions and actions, looking for any local folder, sound, script, or print step.
5. If the rule does not appear at all in Outlook on the web, that is a strong sign it exists only in your desktop Outlook.

Microsoft documents this distinction in its support guidance on managing email messages by using rules in Outlook, including the difference between server-based and client-only rules.

How to Rebuild the Rule So It Runs When Outlook Is Closed

The safest method is to create the new version directly in Outlook on the web. Anything you build there is, by definition, a server rule, because the web interface cannot create client-only rules. Once the new rule works, you can delete the old desktop version to avoid duplicates.

1. Sign in to Outlook on the web with the account that receives the mail.
2. Open Settings, choose Mail, and then choose Rules.
3. Select Add New Rule and give it a clear name that states its job.
4. Add the same conditions as your old rule, such as sender address, subject words, or messages sent only to you.
5. Choose only server actions, such as Move To a folder inside this mailbox, Mark As Read, Pin, Flag, Delete, or Forward To where your organisation permits it.
6. Choose whether to run the rule on messages already in your inbox, if you want it to clean up the mail that arrived while Outlook was closed.
7. Save the rule, then send yourself a test message that matches it from another account.
8. Close desktop Outlook completely, wait for the test message to arrive, and confirm in Outlook on the web or on your phone that the rule acted on it.

If the rule must move mail to a folder, make sure that folder is inside the same server mailbox. A folder in a local archive file looks similar in the desktop folder list, but the server cannot reach into your computer’s hard drive at night. Creating an equivalent folder inside the mailbox itself is often the single change that fixes the whole problem. Our related guide on how to create Outlook rules to automatically sort incoming email covers folder planning in more detail.

What If You Need a Client-Only Action?

Sometimes the thing you want genuinely needs your computer, such as saving attachments into a local folder automatically or printing invoices as they arrive. In that case, no setting can make the rule run while Outlook is closed. You have three realistic options.

Split the work into two rules if you can: a server rule that files and flags the message at any hour, and a client rule that does the local step when Outlook next opens. For urgent processes, ask your IT team about approved server-based automation instead.

Other Reasons a Server Rule May Seem to Stop

• The rule is switched off in the rule list, or a rule above it uses Stop Processing More Rules and catches the message first.
• The conditions are narrower than you think, for example matching an old sender address instead of the one now in use.
• The mailbox is not an Exchange or Microsoft 365 mailbox at all. With POP and IMAP accounts, there is no Exchange server rule system of this kind, so rules depend on the app.

Test with Outlook fully closed, rather than minimised, to get a truthful result, since a minimised program is still running in the background.

Common Mistakes and Helpful Tips

The classic mistake is ignoring the client-only warning during rule creation. That single dialog tells you the rule will not run when Outlook is closed, but it appears at the exact moment most people are hurrying to finish setup. If you see it, stop and remove the local action before saving.

Another mistake is rebuilding the same rule in desktop Outlook with the same local folder and expecting a different result. The creation tool is not the only issue; the actions decide where the rule can live. Building in Outlook on the web is the simplest way to guarantee a server rule.

• Keep server rules simple and focused on one job each.
• Name rules clearly, including the words Server or Local if you keep both types.
• Test every important rule once with Outlook closed before relying on it during holidays.

Conclusion

If your rule runs while Outlook is open but stops when it is closed, you almost certainly have a client-only rule, or a rule tied to a local folder or action. Check whether it appears in Outlook on the web, rebuild it there using only server actions and mailbox folders, and test it with Outlook fully closed. Where a step truly needs your computer, split the rule or accept that Outlook must stay open for that part. Once the rule lives on the server, it will keep sorting your mail around the clock.

Frequently Asked Questions

How can I tell if my Outlook rule is client-only?

Check whether the rule appears in the Rules settings in Outlook on the web. If it is missing there, it is stored only in desktop Outlook. In classic Outlook, the rule description and the warning shown when you created it also indicate client-only status, usually because of a local folder, sound, print, or script action.

Do Outlook rules work when my computer is switched off?

Server-side rules do, because Exchange or Microsoft 365 applies them as mail arrives, independent of your computer. Client-only rules do not. They wait until Outlook is next opened on your computer, at which point they process the waiting messages.

Why does my rule move mail to an archive folder only during the day?

That pattern usually means the archive folder is stored in a local PST file on your computer. The server cannot access that file, so the rule becomes client-only. Move the destination to a folder inside your server mailbox, or let a server rule file the mail and archive it locally later.

Can Gmail or IMAP accounts use server rules in Outlook?

Not in the same Exchange sense. IMAP and POP accounts do not provide this server rule system to Outlook, so rules for those accounts depend on the app being open, or on rules created in the provider’s own web interface, such as filters in Gmail settings.

Will recreating my rule on the web delete the old desktop rule?

No. The two lists can overlap, and the old client-only rule will still exist in desktop Outlook until you remove it. After testing the new server rule, delete or disable the old one so messages are not processed twice or moved in conflicting ways.