Microsoft Lists troubleshooting guide — fix problems fast

A misbehaving Microsoft List usually shows a specific symptom (missing items, a view that won’t load, save errors, or sync failures). Start by identifying the exact symptom and where it appears, then apply the safest fixes first: reload/clear browser cache, restore or recreate a default view, or clear recent JSON formatting. If those don't work, escalate to Recycle Bin restores, repair lookup/column settings, export the schema for inspection, or open a Microsoft support ticket.

What exactly is breaking right now — the symptom checklist

Identify the symptom precisely and where it occurs. A precise symptom points to different causes and tells you which checks and fixes to run first.

• Error banner or dialog in the Lists UI: capture the exact text and timestamp.
• Broken view or formatting: the list opens but columns render incorrectly or a view fails to open.
• Missing items: the list opens but rows are gone or partially present.
• Save or create errors: errors when adding or editing items.
• Sync failures with Teams/SharePoint or Power Automate: flows fail or Teams tab shows stale data.

The exact message varies; capture the banner text or console output when possible.

When the symptom appears:

1. Open the list where the user reported the problem (Lists web app, SharePoint site, or Teams tab). Check the top error banner for a message.
2. If there is no banner, open the browser console (F12) and reproduce the issue to capture network errors or script exceptions.
3. Check Power Automate run history if flows interact with the list.
4. If the list is used inside Teams, open it directly in SharePoint or the Lists app to tell Teams-integration issues apart from list issues.

What specific console codes usually mean:

• 401 / 403: permission or authentication problems.
• 500 series or timeouts: service-side or backend errors.
• JSON parse errors: view or column formatting problems.

Is this the right list and who has access — applicability checks you must run first

Product and scope this guide covers:

• Microsoft Lists in Microsoft 365: the Lists web app, SharePoint Online lists, and Lists inside Teams. This guidance assumes SharePoint Online; on-prem SharePoint behaves differently.

Privileges needed:

• List or Site Owner for most fixes.
• Site Collection Admin or Global Admin for tenant-level checks, PowerShell exports, or when permissions appear inconsistent across the site.

Restart/backup:

• No restart required for the quick checks. If you plan destructive actions (delete, restore, schema export), make a backup or export first.

Quick applicability checks to run now:

1. Verify where the list lives: open the list and confirm Settings > List settings and the site URL.

Settings > List settings

2. Confirm whether the list is a Teams tab view or the canonical SharePoint list: open the Teams tab menu and choose "Open in SharePoint" or open the Lists app and compare the URL.
3. Confirm your permissions: open List settings > Permissions for this list. If you don’t see that option, you lack owner rights.

Settings > List settings > Permissions for this list

4. Check affected users’ license status in the Microsoft 365 admin center if flows, connectors, or access appear blocked.

What these checks tell you:

• If the problem only appears in Teams but not in SharePoint, start with Teams-specific troubleshooting.
• If you see 401/403 in the console, investigate permissions or expired credentials before changing list configuration.

Quick, safe fixes for common problems (start here)

Start with reversible actions that don't change data or schema.

1. Reload and basic browser troubleshooting.

1. Press Ctrl+F5 to force reload the page.
2. Reproduce the issue in an InPrivate/Incognito window.
3. Try a different browser on the same machine.

Expected result: The issue disappears if caused by cached scripts or extensions. If it persists, the cause is server-side or data-related.

2. Clear view filters and restore a default view.

View menu > Edit current view > Remove filters

Expected result: Items reappear or the view loads. If the view is corrupted, create a new standard view from the view menu.

3. Undo recent formatting/JSON safely.

View menu > Format current view > Clear

Expected result: Clearing view formatting restores default rendering. If a column-level JSON is causing errors, clear column formatting the same way.

4. Re-run related Power Automate flows and check run history.

Flow menu > View run history

Expected result: Flows should succeed. If they fail, record the action and error code; permission or schema issues often cause immediate failures.

5. Reapply or reset broken column settings.

Column settings > Edit

Expected result: Verify the data type and lookup references. If a lookup points to a moved or deleted list, re-point or recreate the lookup.

Deeper fixes when quick steps don’t help

If the safe fixes didn't resolve the problem, use corrective actions that affect data or configuration. Test these in a non-production site if possible.

1. Restore deleted items from the Recycle Bin.

Site contents > Recycle Bin

Expected result: Deleted rows are recovered. If not found, check the Site Collection (second-stage) Recycle Bin.

2. Repair lookup and choice column data.

• Check the source list for missing items referenced by lookups. Recreate the missing source items, update the lookup reference, or convert the column to a single line of text if the lookup cannot be fixed.

Expected result: Lookups resolve and views show data. If the source list was moved between sites, you must recreate the lookup or restore the source list.

3. Export/import list schema for inspection.

Exporting and importing can change GUIDs; test in a sandbox site first.

Connect-PnPOnline -Url https://tenant.sharepoint.com/sites/yoursite -Interactive
Get-PnPList -Identity "YourList" | Export-PnPProvisioningTemplate -Out template.xml

Expected result: You get an XML template of the list schema you can inspect or apply to a new list. If export fails, you may lack privileges or an extension is blocking schema access.

4. Disable custom scripts or SPFx extensions temporarily.

• Use the SharePoint admin center or site settings to disable tenant-scoped or site-scoped customizations, then re-enable them one at a time to identify the culprit.

Expected result: If the issue disappears, re-enable extensions one at a time to find the offender.

5. When to escalate to Microsoft Support.

• Escalate for tenant-wide service errors, persistent 500 errors in the browser console with no local cause, or when exports and backups cannot recover expected data. Collect logs, timestamps, and examples before you open a ticket.

How to verify the problem is resolved and what tests to run

Reproduce the original symptom using the same steps the user reported and confirm consistent behaviour across users and clients.

1. Reproduce the original error as the affected user. If the error was a view not loading, open that view and confirm it opens.

View opens without errors and displays X rows

2. Test with another user who previously saw the problem and confirm they can now perform the action.
3. Test in another browser and an Incognito window to rule out client caching.
4. Validate connected services:

• Check Power Automate run history for recent runs and no failures.
• Open the list from Teams and SharePoint to confirm consistent behaviour.

5. Check change history and audit logs for recent schema or permission changes that could explain the issue.

If any test fails, capture the exact error text or console log and revert the last change if possible.

Prevent this from happening again and quick FAQ

Preventive practices:

• Enable versioning on critical lists so you can restore items or fields.
• Schedule regular exports or use PowerShell templates to capture schema snapshots.
• Test JSON column or view formatting in a sandbox list before applying to production.
• Limit chains of lookups and complex calculated columns; they increase fragility and performance costs.
• Monitor Power Automate run histories and set alerts for repeated failures.

FAQ

Q: How do I recover deleted rows quickly?

A: Check the site Recycle Bin first (Site contents > Recycle Bin), then the second-stage (Site collection) Recycle Bin. If not present, restore from a backup or previously exported template if available.

Q: When should I rebuild a list versus restore it from backup?

A: Rebuild when the schema is small and easier to recreate than to clean. Restore when you need to recover large amounts of lost data, item-level metadata, or when GUID continuity is necessary for integrations.

Q: How do list size or item limits affect performance?

A: Large lists with many items and complex views (wide columns, many lookups, complex JSON) will slow rendering and increase the chance of timeouts. Use indexed columns and filtered views to keep queries within supported thresholds.

Conclusion

If quick browser or view resets don’t fix the issue, test deeper fixes in a sandbox: restore from the Recycle Bin, repair lookups, export schema, and disable custom extensions one at a time. If the issue persists with service-side errors, collect logs, timestamps, and examples and open a Microsoft support ticket.

Frequently Asked Questions

What log or trace should I collect before contacting Microsoft Support?

Save the browser console output as text, capture the exact error banner text, record timestamps, note affected site/list URLs, list recent SharePoint or list setting changes, and include any Power Automate run history entries related to the list.

Can JSON column formatting break a list permanently?

JSON formatting can break rendering for specific views or columns but is reversible by clearing formatting. It does not delete data by itself. If JSON references nonexistent fields, remove or correct the JSON and test in a sandbox first.