Microsoft Lists not responding and how to fix it quickly

If Microsoft Lists stops responding, the cause is most often local (browser/profile/cache) or a list/view problem rather than a tenant-wide outage. Start with quick, reversible checks: refresh, sign out/in, clear the browser cache, try another browser or an incognito window. If that doesn't help, check permissions, view complexity or a corrupt item, and then run tenant admin diagnostics (service health, logs, PowerShell) if multiple users are affected.

Is this happening only to me or everyone

Microsoft Lists page hangs or never loads, UI shows spinner or blank pane, or list items do not appear.

When it appears: usually immediately when opening the list in the browser, after navigating in SharePoint or Teams, or when loading a page with an embedded Lists web part.

Check whether the problem is local or service-wide with these tests:

1. Open the same list in another browser on the same machine.
2. Open the list in a private/incognito window.
3. Try the list on a different device on a different network (for example, your phone on mobile data).
4. If you are a tenant admin, check Microsoft 365 Service health for known Lists or SharePoint incidents.

Expected results and next steps:

• If the list loads in another browser or device, the issue is local to the original browser or machine. Follow the quick fixes section.
• If multiple users and networks see the same failure and service health shows an incident, treat it as a service-wide problem and move to admin diagnostics.

Before you start (applicability and safe checks)

• Product/versions: Applies to Microsoft Lists in the Microsoft 365 web app, the Lists app, SharePoint Online, and Lists tabs in Teams.
• Privileges: Basic browser checks require no admin rights. Site or list owner rights help for permission and list checks. Tenant admin rights are required for tenant diagnostics and service health details.
• Restart/backup: No restart or backup is required for the quick checks below. Exporting a list creates a copy you can save.

Safe checks to run first:

1. Try loading the list from a second browser or a private/incognito window.
2. Try loading the list from another device and network so you can tell whether the problem follows your machine or your tenant.

Quick safe fixes to try first (takes 5–10 minutes)

Where to act: your browser. Privilege: none.

1. Refresh the page.
2. Hard reload to bypass cached resources.

Browser menu → More tools → Clear browsing data → Cached images and files (only)

3. Sign out of Microsoft 365, close the browser, then sign back in.
4. Clear the browser cache and cookies for your tenant site.
5. Try another browser (Edge if you used Chrome, or Chrome if you used Edge).
6. Disable extensions or run the browser without extensions temporarily:

• In Chrome: More tools → Extensions → toggle off.
• In Edge: Settings → Extensions → toggle off.

7. Test in an incognito/private window (no extensions, fresh session).

Expected result: the list loads and the UI is responsive. What it means if it did not happen: if the list still hangs in multiple browsers and devices, proceed to permission, view, and admin checks.

If it still hangs: permissions, list size or corrupted items

Where to act: on the list settings and views. Privilege: site owner or list owner helps but is not required for basic checks.

Prerequisites and safe checks:

• No restart or tenant admin rights required for these checks.

Steps to isolate view, permission or item corruption issues:

1. Switch to a simpler view with fewer columns and no calculated fields.
2. Filter the view to a small subset (for example, items created in the last day) and try loading that filtered view.
3. Export the list to Excel to check whether data can be retrieved through export.

List toolbar → Export to Excel

Expected result: an Excel file downloads and opens with rows. What it means if that did not happen: if export fails while the web UI fails, suspect tenant-side corruption or a service problem and move to admin diagnostics.

4. Try opening the list in SharePoint classic view to see if the classic UI renders.
5. Check list permissions: open List settings → Permissions for this list and confirm group membership and permission levels.
6. Look for large attachments, fields with complex JSON column formatting, or recent calculated columns. Temporarily hide those columns in the view and reload.

What it means if these checks fail:

• If a filtered view or export works, the problem is likely a specific view, column formatting, or a bad item. Narrow the problem by removing recently added columns or items one at a time.
• If export and classic view also fail, escalate to tenant admin diagnostics.

When Teams or SharePoint web parts cause the problem

Where to act: the SharePoint page or the Teams tab. Privilege: page editor or site owner.

1. Open the list directly in the Lists web app or the SharePoint site (not the page with the web part). If the list works there, the page or web part is the problem.
2. Edit the SharePoint page that contains the Lists web part and remove the web part temporarily, then publish and reopen the page.
3. Re-add the web part with default settings before applying any custom queries, scripts, or formatting.
4. In Teams, open the list in the native Lists web app or in a browser (not the Teams desktop client) to isolate whether Teams embedding is the issue.
5. Temporarily disable custom page elements or SPFx web parts if present and test again.

Expected results:

• If the list loads after removing the web part, a page customization or web part caused the hang. Reintroduce customizations one at a time to find the cause.
• If the list still fails outside the page, continue with admin diagnostics.

Admin troubleshooting steps and diagnostics

Where to act: Microsoft 365 admin center, SharePoint admin center, or a workstation with admin tools. Privilege: tenant admin or SharePoint admin.

1. Check Microsoft 365 Service health in the admin center for SharePoint/Lists incidents.
2. Look in the SharePoint admin center for tenant-level throttling or known issues.
3. If you can reproduce the failure and need server-side traces, collect correlation IDs from the browser console or the error pane and open a Microsoft Support ticket to get ULS traces correlated to those IDs.
4. Run PowerShell checks to retrieve list metadata. Example PowerShell (run with appropriate tenant access):

Connect-PnPOnline -Url https://yourtenant.sharepoint.com/sites/yoursite -UseWebLogin
Get-PnPList -Identity "Your List" | Format-List Title,ItemCount,EnableVersioning,EnableAttachments

Expected result: the command returns list metadata. What it means if that did not happen: if the PowerShell command times out or errors, that suggests a service or tenant-level problem and you should collect logs and open a support ticket.

5. Check item counts and thresholds with PowerShell:

Get-PnPList -Identity "Your List" | Select Title,@{Name='TotalItems';Expression={$_.ItemCount}}

6. If you find throttling or server-side errors, open a Microsoft 365 support ticket and include correlation IDs, timestamps, tenant name, and exact reproduction steps.

When to open a support ticket: multiple users are impacted across networks, admin diagnostics show errors, or PowerShell queries fail or return unexpected results.

How to verify the fix and prevent it happening again

Verify the fix:

1. Confirm affected users can open the list from their normal browsers and devices.
2. Reproduce the original steps that caused the hang. Expected output: the list opens, views load, and exports succeed.
3. Re-run any PowerShell diagnostics you used earlier; the same commands should return results without timeouts.

What to document and apply to prevent recurrence:

• Root cause: record whether the issue was a browser cache, extension conflict, bad column formatting JSON, corrupt item, oversized attachment, or a service incident.
• Fix applied: document cache cleared, extension disabled, view rebuilt, item removed, columns changed, or support ticket resolution.

Preventive actions:

• Keep list views simple and index columns commonly used for filters.
• Limit large attachments in lists; prefer document libraries for large files.
• Avoid heavy client-side column formatting and complex calculated columns in default views.
• Monitor critical lists by periodic exports and track item counts so you spot growth before thresholds are hit.
• As an admin, enable and monitor service health alerts in the Microsoft 365 admin center and document a support workflow for tenant incidents.

Conclusion

If a quick browser fix gets you back to work, document the root cause and apply the preventive steps above. If the issue persists across devices or PowerShell diagnostics show errors, collect correlation IDs and open a Microsoft 365 support ticket.

Frequently Asked Questions

My list loads for some users but not others—what does that usually mean?

That usually indicates a client-side issue: a specific browser profile, extensions, cached data, or a network/proxy setting. Ask an affected user to try an incognito window, another browser, or a different device; if those work, guide them to clear cache or reset the browser profile.

Can a single corrupt item make an entire list hang?

Yes. A malformed item—large attachments, problematic field values, or bad JSON in column formatting—can cause the modern UI to fail rendering. Narrow the view with filters or export to Excel to locate and remove or fix the problematic item.