Microsoft Lists cannot sync — diagnose and fix fast

Microsoft Lists failing to sync is usually either a local client/browser issue or a server-side problem (SharePoint/OneDrive/tenant settings). Start with quick, reversible actions: refresh, sign out/in, try another client, and clear cache. If that doesn’t fix it, check permissions, list schema and service limits, collect targeted logs, and escalate with the evidence below.

I click sync but nothing happens or I get an error — what exactly is the symptom?

I click Sync and nothing happens

When this appears, check which of these specific behaviors you see and what each usually indicates.

• No UI response when you click Sync: usually a local browser or JavaScript problem, or blocked third-party cookies/extensions.
• “Syncing” spinner never completes: often a network, authentication token, or service-side throttling issue.
• Immediate error dialog or toast with a code: points to permission or API error; capture the exact text and code.
• Partial items missing or attachments not transferring: often schema or column type problems, or a client cache mismatch.
• Export to Excel opens a one-off workbook but does not update later: that’s a snapshot, not a persistent sync.

What to capture now (screenshots, timestamps):

• A screenshot of the error or the stuck spinner, including the browser address bar and time.
• Exact local time and timezone when you reproduced it.
• The URL of the list (copy from address bar).
• Your account name shown in the app (top-right) and the tenant domain if visible.
• If an error code appears, copy it verbatim.

Collect these before you sign out or restart; they help link client events to server logs.

Does Microsoft Lists support the kind of sync you’re trying to do right now? (Applicability)

This guidance applies to Microsoft Lists accessed from SharePoint, Teams and the Microsoft Lists app, and to the OneDrive sync client when it is used for SharePoint document libraries. Privileges needed: user for client steps; site owner or Microsoft 365 admin for permissions, service health and tenant policies. No restart or backup is required for the safest checks listed first.

• Supported flows:
• Lists app or SharePoint list in Teams ↔ the SharePoint list (viewing and editing items) — supported.
• OneDrive sync client applies to SharePoint document libraries and some list experiences but not every list schema.
• Export to Excel is a one-off snapshot and does not provide persistent sync.

Safe checks to run first:

1. Refresh the page and sign out/sign back in.
2. Try a different browser or the Lists mobile/desktop app.

If you need persistent offline sync of list items, confirm the method supports it; many offline or continuous-sync workflows rely on document libraries or Power Automate connectors.

Quick fixes to try first (safe, non-admin steps)

Do these in order — each is reversible and requires no admin rights.

1. Refresh the page or Lists app UI.
2. Sign out and sign back in.

Browser: click your profile photo → Sign out, then sign in again
Lists app: Settings (gear) → Sign out, then sign in

Expected result: UI re-authenticates and sync starts or the error message changes. If nothing changes, continue.

3. Try a different browser or the Lists mobile/desktop app.

• Edge or Chrome are recommended for Microsoft 365 web experiences.

Expected result: If it works in another browser, the issue is local to the original browser (cache, extension).

4. Clear browser cache (or app cache) and retry.

Edge/Chrome: Settings → Privacy and security → Clear browsing data → Cached images and files

Expected result: Eliminates stale scripts; if still broken, issue is not simple cache corruption.

5. Test from another device or network (home vs corporate Wi‑Fi).

Expected result: If another device or network works, suspect local device, VPN, proxy, or conditional access blocking.

If quick steps didn’t work — permission, list schema and service checks

Where to act: SharePoint list settings and Microsoft 365 admin UIs. Privilege: site owner or admin for some checks.

1. Check list permissions and inheritance.

List settings → Permissions for this list

Expected result: Your account is at least Contribute. If you lack permissions, request the site owner to add you or test with a site owner account.

2. Check column types that commonly break sync: Person/Group, Lookup, Managed Metadata, Calculated, Multi-select Choice.

• Problem: Complex or multi-value lookup or managed metadata fields can fail client sync or cause missing items.

What to test: Create a small test list with simple columns (single-line text, date) and try sync.

Expected result: If a simple list syncs, the issue is list schema-related.

3. Large list and threshold limits.

• Problem: Lists over threshold (view/lookup thresholds) may throttle or block certain operations.

What to test: Create a small view or copy a subset of items into a new list and test sync.

Expected result: If small lists work, consider index strategy or splitting data.

4. Licensing and account state.

• Check the user’s license is active and not blocked; check Azure AD sign-in status and any conditional access prompts.

Expected result: If account is blocked or unlicensed, fix that in the admin center.

Temporarily simplifying the list (copying problematic columns to a new list) is a safe way to test schema issues without deleting data.

Client-level and admin-level fixes (cache, sync client, Power Automate and conditional access)

Where to act: user device, Microsoft 365 admin center, Power Automate portal, Intune/Conditional Access. Privilege: user for client fixes; admin for tenant and conditional access.

1. Clear the Lists/Office client cache.

This removes cached credentials and offline data; sign back in after.

Windows: Close the app → %localappdata%\Packages → find Microsoft.MicrosoftLists_... → LocalState → delete cache folders

Expected result: Startup rebuilds cache; if sync still fails, proceed.

2. Update or reinstall the Lists/Office/OneDrive clients.

Office: File → Account → Update Options → Update Now
OneDrive: Settings → About → Version, or reinstall OneDrive from Microsoft

Expected result: Fixed compatibility bugs. If update fails, capture installer or error logs.

3. Check Power Automate flows that write to the list.

Power Automate → My flows → select flow → Run history

Expected result: If a flow is failing or paused and blocking writes, disable it temporarily and test.

4. Review conditional access and device compliance.

Azure AD → Security → Conditional Access → Policies
Intune → Devices → Compliance policies

Expected result: If a policy blocks browser or unmanaged devices, use a compliant device or adjust policy.

5. Check Microsoft 365 Service Health.

Microsoft 365 admin center → Health → Service health

Expected result: If a service outage affects SharePoint or OneDrive, wait for Microsoft to resolve or follow the admin advisory.

6. Reset the sync relationship (unlink/relink).

Unlinking may remove client-side cached offline edits; ensure data is saved or copied first.

Expected result: Re-establishes a fresh sync session. If reset fails, capture logs for escalation.

How to verify the sync is working again and what to collect before escalating

How to confirm success:

• Edit an item in the list on one client, then confirm the edit appears on another client or in the web UI within a few minutes.
• Add a new item on device A and verify it appears on device B and the web.
• Check timestamp fields and Modified By to confirm propagation.

Expected outputs to look for:

• The same content and Modified/Modified By values across clients.
• No sync error toasts after repeated changes.

What logs/traces to collect before escalation:

• Browser console logs and F12 network trace when reproducing the error.

Open dev tools (F12) → Console tab and Network tab → reproduce the action → Save HAR (right-click network → Save all as HAR)

• Lists or Office client logs: gather app log files or use Office diagnostic logging as available.
• SharePoint Unified Audit or Audit logs for the item operations (admin role needed).
• Power Automate run history and failed actions.

Minimum screenshots/messages to provide:

• The stuck spinner or error dialog with timestamp.
• Browser address bar with the list URL and account name.
• F12 network request that returned an error code (screenshot or HAR file).
• If there’s an error code shown, include it verbatim.

When to open a Microsoft support case: after you’ve run the client checks, verified permissions and schema are not the cause, and collected HAR, client logs, list URL, tenant ID and exact timestamps.

How to stop this happening again and quick preventive checks

Practical preventive steps:

• Avoid mixing complex column types in views users will sync (multi-value lookups, managed metadata, calculated fields together). Test new schemas in a sandbox list first.
• Keep large lists under threshold limits or use indexed columns and filtered views to reduce server-side throttling.
• Monitor Power Automate flows that write to lists; add error handling and throttling-aware patterns.
• Keep Office, OneDrive and Lists clients updated by using managed update policies.
• Add a short runbook for on-call IT: check service health, try a different browser, and collect HAR/F12 traces within the first 10 minutes of an incident.

Conclusion

If quick checks don’t restore sync, gather the HAR/F12 trace, client logs, the exact error string or code, the list URL and tenant ID, and a reproducible test (small list that fails). Give these to your site owner, tenant admin or Microsoft Support and open a case only after you’ve ruled out local cache, browser extension, permission or schema issues.

Frequently Asked Questions

Only one user is affected — what could cause that?

If only one user is affected, it’s usually local: expired account token or cached credentials, device conditional access, a browser extension, or their license/role. Reproduce the issue with another account on the same device and with the affected account on another device to isolate it.

How do throttling and large lists affect sync?

Throttling can slow or block API calls; large lists and unindexed views make queries slower and increase throttling. Use indexed columns, smaller views, or split data into multiple lists when necessary.

Does Export to Excel give a persistent sync?

No. Export to Excel produces a snapshot workbook that won’t automatically update with list changes. Use a supported sync method or Power Automate to mirror data if you need continuous updates.

When does Microsoft need to fix a service outage?

If the Microsoft 365 Service Health dashboard shows an outage for SharePoint or OneDrive affecting your tenant, Microsoft will resolve it. Follow the admin center guidance and include any service incident IDs when you escalate.