A scheduled email is still in classic Outlook’s Outbox
You already sent a replacement proposal through webmail. Could the original still waiting on your laptop go out too?
In classic Outlook with Cached Exchange Mode, a delayed message can remain on the computer if the app is closed at the scheduled time. It has not been cancelled: reopening Outlook and reconnecting can send it later. If you already sent a replacement through webmail, delete the unwanted local original before reconnecting the laptop. If the original is still the message you want to send, clear its delivery delay and send it while connected.
What happened between 9 and 10?
Imagine finishing a client proposal the evening before an offsite meeting. You schedule it for 9 a.m., shut down, and leave. At 10, you open Outlook and the message finally goes. The recipient has been waiting while the finished proposal sat on your computer. This is a hypothetical example, but the question is real: a Microsoft Q&A user in February 2025 asked whether scheduled mail would send with the laptop off, then clarified that they used the Microsoft 365 desktop app.
Microsoft documents a specific failure: Do not deliver before with Cached Exchange Mode, when Outlook is not running at the scheduled time. The delayed message is held in the local .ost Outbox rather than deferred on the server. Starting Outlook later lets that local queue be processed. The same article explicitly excludes the account's Online mode from this problem.
That explains why a company email address alone cannot answer the shutdown question. The address tells you who is sending; it does not identify which scheduling mechanism was used. Keep the intended time and actual delivery time separate when explaining a missed deadline to the client.
Identify the app and sending account
On Windows, first distinguish new Outlook from classic Outlook. Microsoft's version guide points to Settings at the top right in the new app and the File menu in classic. A browser session is another route. “I have Microsoft 365” is insufficient when a colleague is trying to reproduce the problem.
In classic Outlook, inspect the relevant Exchange account through File → Account Settings → Account Settings → Change. Look for Cached Exchange Mode; do not change it just to identify it. Microsoft describes caching as the default and recommended configuration for Exchange and Microsoft 365 accounts. New Outlook does not have that same mode.
If you have personal and work accounts in one app, record the From address on the delayed message. Checking the work account's settings tells you little about a message sent through the personal account. Include the menu you used to schedule it in any support request.
Also distinguish caching from being disconnected. Cached Outlook can be connected to the server. In classic Outlook, a highlighted Work Offline button or the status bar's offline message indicates a different condition. Microsoft's offline guide explains those indicators. A working browser connection is not proof that Outlook has connected successfully.
Find the pending original before composing again
Search under the account that sent the message. Use the scheduling route to choose the folder:
| Scheduling route | Where to look | What to inspect |
|---|---|---|
| Classic Delay Delivery | Outbox | Do not deliver before date and time |
| Ordinary Schedule send in new Outlook or the web | Drafts | Scheduled time and scheduling controls |
| Viva Insights suggestion | Sent Items on Windows; Drafts on the web | Pending schedule and Send now or Don't send controls |
The first two routes follow the general scheduling instructions. The third follows the separate Viva Insights guidance. With that third route, Sent Items is not conclusive evidence that the recipient already has the message.
A draft is not automatically a scheduled message either. You may have saved the text without completing the scheduling action. Open it and inspect the time and status. If two drafts share a subject, compare recipients and attachments before deciding which is the original.
Nor does an Outbox entry prove that you used classic Delay Delivery. New Outlook's offline functionality also allows messages to enter an Outbox. Folder location is useful alongside the app and menu you identified, not as a substitute for them.
Resend without creating two deliveries
At 10 a.m., decide whether yesterday's proposal is still correct. Perhaps the price changed during the morning meeting. Restoring connectivity to send the old attachment may now be the wrong outcome, even if it fixes the delivery delay.
If you already sent a replacement and the laptop is still off, disconnect Wi-Fi and wired networking before starting Outlook. This lets you deal with the local original before reconnecting. Open classic Outlook, check Work Offline on Send/Receive, and delete the unwanted message from Outbox. Deletion moves it to Deleted Items. Confirm that it has left Outbox before restoring the network and online operation. Deleting this item does not recall anything already delivered.
For a classic delayed message that should go immediately, open the original, clear Do not deliver before in its options, close the options, and select Send. Outlook needs a connection. In new Outlook, open the scheduled draft and use Cancel send before revising or sending it.
The separate web scheduling guide also documents an edit pencil followed by Send Now. Follow the controls displayed for your pending message; do not assume every Outlook screen uses the same label.
Consider a replacement sent through the browser while the laptop remains off. If the old delayed message is still queued locally, starting the laptop later can send another copy. The two attachments might even contain different prices. Resolve the pending original before scheduling its replacement. If delivery is uncertain, check the sending record and ask the recipient before creating another message.
For a pending Viva-scheduled message you no longer want to send, choose Don't send to move it to Deleted Items. To release the original early, choose Send now. These controls act on a message still waiting to go out; they do not recall one already delivered.
Online mode is an exception to this caching problem
If you keep classic Delay Delivery with caching, plan around the app remaining running and connected. An overnight shutdown or a morning spent travelling may make that unsuitable. Closing the lid is not a reliable substitute for checking the computer's power behavior.
Exchange's Online mode is an exception to the documented caching failure, but switching modes affects more than one scheduled message. Caching provides a local mailbox copy when connectivity is poor. Bring the administrator your actual requirement—sending while the laptop is off—before changing the account's normal configuration.
If the account already uses Online mode, a local cached queue is not a sufficient diagnosis. Check the sending account's connection and the original message's delivery options, then give support the restart and delivery times. A message remaining in Outbox does not establish that every send failure has the same cause.
Record whether restarting releases the delayed message
To reproduce the classic cached-mode delay for support, use a harmless message without attachments and a mailbox you can check independently. Use the same From account and Delay Delivery option involved in the missed schedule. This checks the failure described above; it does not replace the documented explanation.
- Schedule a few minutes ahead. Record the displayed date, time, and pending folder.
- Close the app and shut down as you normally would after work.
- After the scheduled time, check the receiving mailbox on another device before restarting the sending computer.
- If nothing arrived, note that result. Then restart Outlook and record whether delivery follows.
A compact record might say: “Work account A, classic Delay Delivery, cache enabled, scheduled 14:10, laptop off, absent at 14:12, arrived after Outlook opened at 14:15.” Those times are illustrative. If the message remains missing after Outlook reconnects, record that result too.
Inspect receipt on the other device rather than waking the sending laptop just to look. Otherwise your observation can trigger the very delivery you are testing. A successful result establishes what happened under that particular setup, rather than proving every account works identically.
If the result is inconsistent, give support the test subject, sending address, app version, scheduling route, intended time, and observed arrival time. Avoid a ticket that says only “scheduled mail is broken.” For example, a missing test message while the laptop is off and an immediate arrival after restarting it gives support a different starting point from a message still missing after reconnection. Keep the original pending item available for inspection rather than repeatedly replacing it and losing the sequence of events.
If a replacement has already gone out, identify the final attachment for the recipient and confirm that the old pending message has been dealt with. If two proposals with different prices were delivered, explicitly state which price and delivery date apply.