> ## Content Index > Fetch the complete content index at: https://todayfixtech.com/llms.txt > Use this file to discover other available public pages before exploring further. # Microsoft Lists freezing — quick checks to restore it - URL: https://todayfixtech.com/microsoft-lists-freezing/ - Published: 2026-10-30T06:48:48.000Z - Updated: 2026-10-30T06:48:48.000Z - Author: Md Sojib Mia - Tags: Troubleshooting [Microsoft Lists freezes are](https://todayfixtech.com/fix-microsoft-365-login-issues/) almost always a client-side rendering or view-performance issue you can fix quickly by reloading, trying a private/incognito window, switching browsers or opening the list outside Teams. If quick checks don’t help, simplify the list view (remove heavy JSON formatting, lookup/calculated columns, or very large views) and collect console/Network logs before asking your tenant admin or Microsoft Support. ## Is the freeze happening right now and to everyone or just you? ```text Lists UI becomes unresponsive (clicks do nothing, scrolling freezes, edits won't save) or the page shows a spinner and never completes. ``` Symptom Quick check: determine whether the issue is local to your device/account or tenant-wide. Do these in this order to get a decisive result fast. 1. Open a private/incognito browser window and load the same list URL. ```text Browser -> New Private/Incognito Window ``` Settings path 1. Try the list URL on a different device (phone or another PC) and with a different account if possible. 2. If you use Teams, open the same list via the SharePoint site URL (use "Open in browser" from the Teams tab). 3. Check Microsoft 365 Service Health in the Microsoft 365 admin center (admins) or ask your tenant admin to check the Message Center for incidents. Expected results and interpretation: - If the list works in a private window or on another device, the problem is local to your browser, profile, or network. Proceed to the browser/extension/network checks. - If the list is slow or frozen everywhere for multiple users, treat it as a tenant or service-side issue and escalate to your tenant admin to check service health, recent deployments, or throttling. If you can’t access the admin center, ask an admin to check Service Health and Message Center for incidents affecting Lists, SharePoint, or Teams. ## Could this be the web browser, Teams client, or a bad app update? Before you start: [this applies to Microsoft](https://todayfixtech.com/fix-onedrive-slow-performance/) Lists in modern browsers (Edge, Chrome, Firefox), Lists inside Teams, the Lists mobile app, and the SharePoint list view in desktop. No special privileges are required for the checks below; they won’t make permanent changes. Start by isolating the client. 1. Switch browsers: open the list in Edge, Chrome, and Firefox. If it works in one browser but not another, the problem is browser-specific. 2. Disable browser extensions (especially ad blockers, script blockers, or privacy extensions) or run a private window where extensions are usually disabled. 3. Update the browser and the Teams client to the latest version and restart them. 4. Try the Lists mobile app or open the underlying SharePoint list URL in a browser — the SharePoint view often uses the same rendering and can confirm whether the issue is Lists-specific or SharePoint-side. 5. If the list is shown inside Teams, open the list in the browser using "Open in browser" from the Teams tab to compare behavior. Example: an aggressive ad-blocker or a script [blocker can block Microsoft](https://todayfixtech.com/microsoft-365-tips-tricks/) scripts and cause freezes. If disabling extensions fixes it, re-enable them one at a time to find the culprit. Expected results and interpretation: - If disabling extensions or switching browser fixes the freeze, keep the working browser profile or remove the conflicting extension. - If the problem appears after a recent Teams or browser update and started for multiple users, check Service Health and consider using the browser temporarily while waiting for a patch. If you suspect a bad Teams client update, use the browser version to continue working while you gather logs. ## Quick fixes to try first (safe and fast) These are the least disruptive steps. Each step includes expected time and what success looks like. 1. Reload the page. ```text Page reload completes without long stalls; list rows render and you can click cells. ``` Expected output Time: 5–10 seconds. Success: UI responds immediately after reload. If it still freezes, continue. 1. Open the list in an Incognito/Private window. ```text Browser -> New Incognito/Private Window ``` Settings path Time: 10–30 seconds. Success: list loads normally in private mode — suggests an extension or cached data issue. 1. Clear the browser cache for the site (site data only). ```text Browser -> Settings -> Privacy & security -> Clear browsing data -> Cookies and other site data / Cached images and files (select site) ``` Settings path Time: 30 seconds–2 minutes. Success: refreshed resources load and responsiveness returns. If not, proceed. 1. Restart the browser or the Teams client and sign out/sign back in. ```text Teams -> Profile -> Sign out Browser -> Close all windows, reopen ``` Settings path Time: 1–3 minutes. Success: persistent sessions or stale tokens cleared; UI behaves normally. If the Teams tab was the problem, open the list in a browser. 1. Test a different network (switch from corporate VPN/Wi-Fi to a mobile hotspot). Time: 1–5 minutes. Success: if the list works on another network, the issue might be network-related (proxy, firewall, or throttling). Contact your network/IT team. What it means if these steps don’t help: move to deeper fixes that examine list structure, view complexity, or tenant-side issues. ## Deeper fixes when quick steps don’t help Where to act: the list settings in SharePoint/Lists and your browser dev tools. Privilege: list owner or site owner helps but you can test as a user by switching to a simple view. Check for heavy list constructs that commonly cause freezes. - Large views: views that return thousands of items can be slow. Create or switch to a view that filters to fewer items or use indexed columns. 1. Switch to a simple default view (no grouping, no complex filters). ```text List -> All items view dropdown -> Select simple view (or Create view -> Standard view -> no formatting) ``` Settings path Expected result: if responsiveness returns, the original view is the problem. - Conditional formatting and JSON column formatting: complex JSON and many conditional rules are evaluated client-side and can hang the UI. Temporarily remove or disable formatting. 1. Edit view or column formatting and clear the JSON. ```text Column settings -> Format this column -> Clear JSON View settings -> Format current view -> Clear JSON ``` Settings path Expected result: list becomes responsive; if so, simplify or optimize the JSON. - Lookup columns, calculated fields, and lookups to large lists: many lookups or complex calculated fields slow rendering. 1. Create a view that hides those columns or temporarily remove them from the view. ```text List -> Edit current view -> Uncheck lookup/calculated columns under Columns ``` Settings path Expected result: if the UI is responsive without those columns, plan to reduce lookups or denormalize data. - Large attachments or rich fields: attachments and complex multi-line fields increase render time. Use a simple view that hides them. If none of these reduce freezes, ask your tenant admin to check for throttling, resource limits, or recent deployment changes in the tenant. Admins can also check the SharePoint Online health dashboard and open a support case with Microsoft including tenant details. ## Verify the problem is fixed and collect evidence if it’s not How to confirm: perform a short checklist of normal actions and note expected behavior. - Open several rows, edit a field, save, sort a column, apply a filter, and paginate through results. Each action should complete within a few seconds. - If you see delays or errors, reproduce the problem in a controlled way and collect evidence before escalating. Collect these items for IT or Microsoft support: - Exact steps to reproduce (step-by-step) including which view, which columns, and the approximate number of items. - Screenshots or a short screen recording showing the freeze and timestamps. - Browser console logs: open Developer Tools -> Console and copy errors. Also capture the Network tab waterfall for the page load and the failed or slow requests. ```text Browser -> F12 -> Console / Network -> Right-click -> Save as HAR with content ``` Settings path - Teams logs (if using Teams): in Teams, press Ctrl+Alt+Shift+1 to collect logs or follow your org’s method for Teams diagnostics. - Note the browser name/version, Teams version, OS, time (with timezone), and whether a VPN was in use. Expected verification: after removing the suspected cause (formatting, columns, view complexity), the actions above complete normally. If not, include the captured logs and reproduction steps when you escalate. Don’t edit or delete the list while troubleshooting unless you have backups or explicit approval; that can lose evidence. ## Prevent this in the future and when to escalate Prevention tips you can apply right away: - Keep views small: use filters to return fewer rows, preferably under a few thousand visible items, and use pagination. - Index columns used in filters and sorts to avoid full scans. - Simplify or limit conditional and JSON formatting. Test formatting on smaller views first. - Reduce the number of lookup and calculated columns displayed in a single view. - Split very large lists into multiple lists or use a document library if attachments dominate. When to escalate and what to send: - Contact your tenant admin when multiple users are affected, when you suspect service-side throttling, or when admin-level diagnostics (Service Health, tenant logs) are needed. - Open a Microsoft support ticket when you have: reproduction steps, browser/Teams versions, HAR file or network logs, console errors, timestamps, and screenshots. That evidence speeds diagnosis. - Post to admin support channels (your internal IT, Microsoft 365 admin community) with the same evidence. If an incident is identified, follow the admin center guidance for mitigations. Do not delete lists or major columns as a first step. Only remove or simplify columns and formatting temporarily for testing and with consent when you’re sure it’s safe to change. ## Before you start (applicability and safe checks) Applies to: Microsoft Lists in modern browsers (Edge, Chrome, Firefox), Microsoft Teams desktop client and Teams tab hosting Lists, Lists mobile app, and the SharePoint list view in desktop. The exact UI and bug surface can vary slightly between the browser engine and the Teams embedded webview. Privileges needed: normal user checks require no elevated privileges. List owner or site owner privileges are helpful for changing views or formatting but not required for initial testing. Restart/backup: these steps do not require backups. Avoid deleting or permanently changing list schema or data while collecting evidence. Safe checks to do first: - Open the list in a private/incognito window. ```text Browser -> New Private/Incognito Window ``` Settings path - Try the list in another browser or on another device. - Check with one other user whether they see the same freeze. If those quick checks pass, proceed with browser, formatting, and view checks described above. ## Conclusion If a reload, private window, or switching client fixes it, keep working in that client while you simplify the list view. If not, collect console/Network logs, HAR files, Teams logs and exact reproduction steps, then escalate to your tenant admin or Microsoft Support with that evidence. ## Frequently Asked Questions ### Why does Lists freeze only in Teams and not in the browser? Teams hosts web content in an embedded browser engine and adds its own authentication and caching. A Teams-specific cache, an outdated Teams client, or a Teams-only extension can cause freezes while the same URL works directly in a full browser. Test by opening the list in the browser and collect Teams logs if the issue is Teams-only. ### Will removing JSON formatting delete my data? Clearing JSON column or view formatting only removes the client-side presentation rules; it does not delete list items or field values. Still, avoid permanent edits until you have approval or a backup plan. ### I’m an admin — what tenant checks should I run? Check Microsoft 365 Service Health and Message Center for incidents, review recent configuration or policy changes, look for throttling alerts in SharePoint reports, and request HAR files, console logs, and timestamps from affected users to correlate client failures with tenant events.