Microsoft Lists stuck: diagnose & fix freezes, save issues

If Microsoft Lists is freezing, not saving edits, or pages are unresponsive, the cause is usually local (browser, cache, network) or a tenant/list configuration issue such as permissions, large views, JSON formatting, or a misbehaving Power Automate flow. Start with quick, reversible checks (another browser/incognito, clear cache, sign out/in, try a different network) and then move to admin-level checks (list indexing, reindex, disable flows, check SharePoint site health) before escalating to Microsoft support.

Is this a one-off freeze or a wider outage

Lists page hangs, buttons don't respond, edits show a spinning indicator or 'Saving...' indefinitely, or views fail to load.

When it appears

This can happen immediately after opening a list, after saving or editing an item, or when switching views.

Quick scope checks (do these first)

1. Reproduce on another browser or device.
2. Ask one colleague in the same tenant to open the same list and perform a simple edit.
3. Check Microsoft 365 Service health from the admin center (if you have admin access) or use a public outage tracker.
4. Test responsiveness of other Microsoft 365 apps (SharePoint site pages, Outlook web).

What the outcomes mean

• If the list works in another browser/device but not yours: likely local (browser, cache, extensions, network). Proceed to Quick safe fixes.
• If a colleague in the same tenant sees the same problem but others don't: likely tenant configuration, a list-level issue, or a Power Platform flow affecting behavior.
• If multiple tenants report the same issue or Service health shows an incident: a Microsoft outage — monitor service health and escalate only if business-critical and the incident persists.

Before you start

Applies to

• Microsoft Lists (lists.microsoft.com) and SharePoint modern lists.

Privileges and required restart/backup

• End-user checks: no special privilege required.
• Site Owner or List Owner: required to change list settings and check permissions.
• SharePoint admin or Global admin: required for site collection health and admin center diagnostics.
• Restart/backup: no restart or backup required for initial inspection steps.

Two safe checks to do first

1. Try the list in an Incognito/private window or another browser.
2. Ask one colleague to reproduce the issue on their machine.

Could it be permissions, list size or view settings

Applies to

• Microsoft Lists accessed via lists.microsoft.com or SharePoint lists.

Privileges and safe checks

• You need at least List Owner or Site Owner to change list settings and check permissions. For some site health checks you need SharePoint admin or Global admin.
• No restart or backup is required for inspection steps. Don’t change permissions or delete columns yet; only observe.

What to look for

• Large list size: lists with many items (especially without indexed columns) can stall views or time out.
• Complex views: many lookup columns, calculated fields, or filters on non-indexed columns increase load and can cause slow or failed renders.
• Custom formatting: malformed JSON column or row formatting can break view rendering.
• Broken or unique permissions: unique item or list permissions can slow access while SharePoint resolves access checks.

How to spot these

1. Open List settings > Columns and scan for Lookup, Person/Group, or calculated columns.

Site contents > [Your list] > Settings (gear) > List settings > Columns

Expected result: you can see column types. If this page fails to load, the issue is likely larger (site or service-level).

2. Check Views for filters and sort orders on the default view.

Site contents > [Your list] > Settings > List settings > Views

Expected result: view definitions are visible. If the default view shows all items without indexed filters, performance may be poor.

3. Inspect Site Permissions to see if the list uses unique permissions.

Site contents > Site settings > Site permissions

Expected result: permission groups and unique permissions are visible. If permissions are broken, expect delays while SharePoint evaluates access.

If you find complex formatting, many lookup columns, or non-indexed filters, those are likely causes — proceed with the safe fixes below before changing configuration.

Quick safe fixes to try first

Where to act: your browser or the client machine. Privilege: end-user. These actions are reversible.

1. Hard reload and sign out/in

1.1 Perform a hard reload.

Browser: Ctrl+F5 (Windows) or Shift+Reload (macOS)

Expected result: page reloads fully and transient script errors clear. If the page still hangs, continue to step 2.

1.2 Sign out from Microsoft 365 in the browser and sign back in.

Expected result: authentication cookies refresh. If sign-in fails, the issue may be Conditional Access or SSO.

2. Test Incognito/private window and another browser

2.1 Open the list in a private/incognito window or in a different browser (Edge, Chrome, Firefox).

Expected result: if the list loads normally, the problem is browser-specific (extensions, profile cache). If it still hangs, the problem is broader.

3. Clear browser cache and disable extensions

3.1 Clear cache and cookies for the site.

Browser settings > Privacy & security > Clear browsing data > Cached images and files, Cookies and other site data

Expected result: stale script files are removed and a fresh copy is fetched. If clearing doesn’t help, disable extensions and retry.

4. Try a different client

4.1 Use the Microsoft Lists app or a different browser.

Expected result: if a different client works, use it and report the faulty browser profile for cleanup.

5. Check network and Conditional Access

• Try a different network (mobile hotspot) to rule out proxy or firewall issues.
• If you suspect Conditional Access, contact your IT security team to confirm policies that might block the client.

6. Simple permission reset (for owners)

6.1 Re-add yourself or a group temporarily to the list Owners group (do not remove existing permissions).

Site contents > [Your list] > Settings > List settings > Permissions for this list

Expected result: if permissions were the cause, access and edits should be responsive. If not, revert the change and continue with advanced checks.

These steps are non-destructive. Avoid deleting columns, flows, or disabling site features at this stage.

Advanced troubleshooting for admins and power users

Where to act: SharePoint admin center, site collection, Power Platform, or as a site owner. Privilege: Site Owner or SharePoint admin for many steps.

1. Check site collection health and storage

1.1 In the SharePoint admin center, review site health and storage metrics for the site hosting the list.

Expected result: identify quota or health warnings. If the site shows unhealthy diagnostics, open a support ticket with Microsoft and include site diagnostics.

2. Inspect list thresholds and indexing

2.1 Verify whether views rely on non-indexed columns and whether the list crosses threshold limits for operations.

Site contents > [Your list] > Settings > List settings > Indexed columns

Expected result: add indexes to frequently filtered columns. If indexing fails because of list size or errors, consider filtered views, folders, or contact SharePoint admin.

3. Disable custom column formatting and JSON row formatting

3.1 Temporarily remove or revert JSON formatting on columns and views.

Site contents > [Your list] > Column settings > Format this column > Clear formatting

Expected result: if malformed JSON caused the freeze, the list should load normally after removing formatting. If not, reapply formatting only after testing in a staging list.

4. Disable Power Automate flows and Power Platform connectors

Disabling or deleting flows can interrupt business processes. Only disable temporarily and document the state before change.

4.1 Turn off any flows that trigger on item create/update for this list.

Power Automate > My flows > [flow] > Turn off

Expected result: if a flow is misbehaving (infinite loop or external call failing), disabling it should restore responsiveness. If disabling fixes the issue, inspect the flow’s run history for errors.

5. Reindex the list and run health checks

5.1 Reindex the list to force SharePoint to rebuild searchable and queryable metadata.

Site contents > [Your list] > Settings > List settings > Advanced settings > Reindex List

Expected result: queries that previously timed out may succeed once indexing completes. If reindexing fails or takes excessive time, escalate to a SharePoint admin.

6. Inspect browser console and network traces

6.1 Open the browser DevTools (F12), reproduce the issue, and note console errors and failed network calls.

# Not a command; use browser DevTools Console and Network panels

Expected result: JavaScript errors, failed API requests (HTTP 4xx/5xx) or long-running XHR calls reveal the failing component (client script, SharePoint REST, Graph API, or a connector). If errors reference specific resources (for example, _api/web/lists), collect those messages for escalation.

7. Create a temporary lightweight view or list

7.1 Create a simple view that shows a few indexed columns and a small item limit.

Site contents > [Your list] > Create view > Standard view > Select minimal columns > Item Limit: 100

Expected result: if the lightweight view loads, the problem is the default view or data volume. Use the lightweight view to allow edits while you fix the root cause.

How to verify the problem is fixed and prevent it

Verify the fix

1. Create, edit, and save an item using the same client and view that previously failed.

Expected result: item saves without indefinite 'Saving...' and appears in the view.

2. Load both the slow/default view and the limited view you created earlier.

Expected result: both views load within acceptable time and actions (edit, delete) complete.

3. Reproduce the action that previously triggered the freeze (for example, bulk edit or sort by a lookup column).

Expected result: no freeze and no persistent script errors in the console.

Prevent recurrence (practical steps)

• Index frequently filtered columns to keep queries under thresholds.
• Limit default view item count; use pagination or an item limit in views.
• Reduce lookup and calculated columns in commonly used views.
• Test heavy JSON formatting in a staging list before applying to production.
• Review Power Automate flows: avoid long-running synchronous calls and add error handling and throttling.

Monitoring tips

• Use the SharePoint admin center to monitor site storage and health.
• Periodically review run histories for flows connected to critical lists.
• Keep a documented fallback view that shows minimal columns and can be used if the default view breaks.

When to collect logs and escalate to Microsoft support

What to collect before escalating

• Exact reproduction steps with timestamps.
• Screenshots or short screen recordings showing the freeze and any error messages.
• Browser console output from DevTools (Console) and failed network requests from the Network panel. Copy error text and request URLs.
• Power Automate run history entries for flows tied to the list (include expanded error details).
• SharePoint site diagnostics: site URL, site collection ID, list ID (from the list settings URL), and any admin center warnings.
• User accounts affected and whether the problem is tenant-wide or isolated.

How to capture useful artifacts

1. Browser console: open DevTools (F12) → reproduce → right-click Console → Save as.
2. Network trace: reproduce with DevTools Network tab open → right-click → Save all as HAR.
3. Power Automate: open the flow run that matches the time of the issue and export run details.
4. SharePoint: copy the list settings URL; the list GUID is in the query string List=.

What to include in the support ticket

• Short summary: what happens, when it started, how many users affected.
• Steps to reproduce and expected vs actual behavior.
• Attachments: console log, HAR file, screenshots, flow run logs, and the list GUID and site URL.

Where to open a ticket

• Tenant admins: open a support request in the Microsoft 365 admin center under Support > New service request.
• If you have a paid support contract, use that escalation channel and include the artifacts above.

What to expect from Microsoft support

• Microsoft will ask for the artifacts above and may request a network capture or temporary access to the tenant for diagnostics. Be ready to provide precise reproduction steps and timeframe.

Conclusion

If quick, reversible fixes don’t fix the problem, move to admin checks: indexing, reindex, disable flows temporarily, remove formatting, and check site health. Collect console logs, HAR files, flow run details, the list GUID and site URL before contacting Microsoft support — those artifacts speed diagnosis. Escalate through your tenant admin if the issue affects many users or matches an active service incident.

Frequently Asked Questions

Why does Lists freeze only for some views?

Views that return many items, use non-indexed filters, or include many lookup/complex columns place heavier load on SharePoint queries. A view with large result sets or heavy JSON formatting is more likely to time out; create a limited, indexed view to confirm and use that while you fix the default view.

Can Power Automate flows cause Lists to hang?

Yes. A flow that triggers on item create/update and performs synchronous calls, loops, or external API calls can delay or block operations. Temporarily disable relevant flows and inspect their run history for infinite loops or external failures to confirm.