How to Fix Yammer Feed Loading Issues on Desktop Browsers
Question details
The user is unable to load the Yammer feed on desktop web browsers, encountering a persistent reload error, despite the application functioning correctly on mobile devices.

- Product
- Microsoft Yammer (Viva Engage)
- Device & OS
- Desktop
- Scenario
- Attempting to access and view the Yammer network feed via desktop web browsers.
- Observed behavior
- The Yammer feed fails to load and displays a reload error across multiple desktop browsers and computers, while remaining fully accessible and functional on mobile devices.
Before escalating the issue, clear your desktop browser cache and try logging into Yammer using an Incognito or InPrivate browsing window to rule out local browser extension conflicts.
Request Administrator Support via Microsoft 365 Admin Center
Since the reload error spans multiple desktop environments but excludes mobile, it requires investigation of tenant settings and service health logs by a Microsoft 365 administrator.
When a Yammer feed reload error occurs across different desktop browsers and computers simultaneously, it strongly indicates a tenant-specific configuration issue or a temporary backend Microsoft service degradation.
End users cannot resolve backend tenant issues locally. The most effective resolution is for your organization's IT department to escalate the incident directly to Microsoft Support for a thorough investigation of tenant settings and server-side service logs.
Take note of the exact error message on your desktop, and confirm that your Yammer mobile app is still syncing correctly.
Reach out to your designated Microsoft 365 administrator or IT helpdesk, informing them that the Yammer feed is experiencing a desktop-specific reload failure across multiple browsers.
The administrator must log into the Microsoft 365 Admin Center, navigate to the 'Support' tab on the left menu, select 'New service request', and provide the details of the desktop-specific Yammer routing issue.

Maintain Team Productivity with WPS Office
While you wait for your Microsoft 365 administrator to resolve the Yammer feed access issue, keep your team's document collaboration running smoothly. WPS Office is a powerful, lightweight alternative to Microsoft Office that lets you effortlessly create, edit, and share documents for free.
- 1. Download the Application: Visit the official WPS website and download the free WPS Office installer for your desktop device.
- 2. Open Existing Documents: Launch WPS Office and open your existing Microsoft Office files; your formatting and layouts will be perfectly preserved.
- 3. Collaborate Effectively: Use WPS Cloud to share document links with your team, ensuring continuous workflow even when other communication platforms are temporarily down.

Frequently Asked Questions
Why does Yammer work on my phone but display a reload error on my computer?
Mobile applications use different authentication tokens, APIs, and caching mechanisms than web browsers. A desktop-only failure usually points to browser-specific security policies, tenant web configuration errors, or a targeted Microsoft web service degradation.
Can clearing my browser cache fix the Yammer desktop reload error?
If the issue is isolated to just one specific browser on your computer, clearing the cache and cookies may fix it. However, if the error persists across multiple browsers (like Chrome, Edge, and Firefox) and computers, it is highly likely a backend service issue requiring admin intervention.
How can I check if Yammer is experiencing a widespread outage?
Standard users can check third-party status tracking websites like Downdetector to see if others are reporting Yammer outages. The most reliable method, however, is asking your IT administrator to check the official Service Health Dashboard inside the Microsoft 365 Admin Center.
What details should I provide to my IT admin when reporting this Yammer issue?
To help your admin investigate quickly, provide the exact error text you see, a list of the desktop browsers you have tested, confirmation that the mobile app is still working, and the approximate time the loading issue began.




