Using New Outlook on Windows for professional communication and productivity
This issue occurs when authentication partially times out, such as when an attachment is being fetched in the background and fails with a 440 error. The current workaround is to sign out and sign back into your Microsoft account.
It’s frustrating that end-users constantly have to provide detailed instructions and reproduction steps when these issues should be identifiable within your code. It feels like all responsibility is shifted onto users while little effort is made on your end to proactively resolve them.
Microsoft still struggles with proper session management. For example in Teams, even after a session has expired across all devices, users may still receive mobile notifications, even though re-authentication is required. An absolutely trash implementation.
This issue seems to extend here as well. The session appears to be in a partially logged-in/logged-out state: you can browse and refresh your emails, but when attempting to open one and fetch an attachment, an error occurs. The Web App then attempts to resolve it by refreshing the page, assuming the sign-in page will appear if the session has expired.