> ## 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 not syncing — fix changes not appearing - URL: https://todayfixtech.com/microsoft-lists-not-syncing/ - Published: 2026-10-30T07:01:53.000Z - Updated: 2026-10-30T07:01:53.000Z - Author: Md Sojib Mia - Tags: Troubleshooting If edits [you make in Microsoft](https://todayfixtech.com/fix-microsoft-365-login-issues/) Lists don’t appear in Teams, SharePoint, or the Lists app, the cause is usually a break in the sync path (client cache, token/auth issue, or a backend replication delay). Start with quick checks: refresh, sign out/in, confirm Microsoft 365 service health and your Edit permissions; then clear caches or re-link clients only if those steps fail. The guidance below runs safe fixes first and moves to deeper actions, with verification steps so you can confirm the list and all items are intact. ## I open the list and my changes don’t appear in Teams or SharePoint — what symptom should I check first? Symptom ```text Missing rows after an edit Delayed updates (changes appear in one client but not others) Conflict markers or "this item has changes" messages Items available online but not offline, or vice versa ``` Symptom When it appears - Right after you edit an item: if the change doesn't show in another client within a minute or two, treat it as a sync issue. - When the item saves locally but shows an error only in other clients: that suggests replication, permission, or token problems. Quick single-sentence test to classify the problem 1. Edit a non-critical field on one item in the browser (SharePoint UI) and then immediately open the same item in Teams and the Lists mobile app. If the change appears in the browser but not in the other clients, it’s a client cache or replication delay issue; if no client shows the change, the server write failed. ## Is this problem even about syncing or something else? Before you start - Product/versions this applies to: Microsoft Lists (browser and mobile), Lists app in Teams, SharePoint lists, OneDrive/SharePoint sync client. - Privileges: you need at least Edit permission on the list. Admin privileges are not required for the basic checks; some deeper checks (audit logs, conditional access) need admin rights. - Restart/backup: the quick checks are read-only and low-risk; no backup required. For steps that unlink a sync client, ensure there are no unsynced local changes. Quick elimination checklist - Service health: check Microsoft 365 service health in the admin center to rule out outages. - Permissions: confirm you have Edit access on the list and the site; a viewer can’t save changes. - Wrong view or filtered page: confirm you’re looking at the same list and view (personal views and filters can hide items). - Cached page: try a hard refresh in the browser (Ctrl+F5) or open the list in a private/incognito window. - Other users: ask a colleague with similar permissions to edit the list. If they see different behavior, the issue is client-specific. If these checks look normal, proceed to the quick fixes. ## Safe first-aid fixes I should try now (fast checks that often fix it) Where to act and expected result 1. Refresh the browser or re-open the list in a private window. ```text Browser > Address bar > hit Ctrl+F5 (or open a new incognito/private window) ``` Settings path Expected result: the list reflects the latest changes. If it does not, continue. 1. Sign out of the app (Teams/Lists/SharePoint) and sign back in. ```text Teams > Profile > Sign out SharePoint/Lists web > Profile > Sign out Lists mobile > Settings > Sign out ``` Settings path Expected result: authentication tokens refresh and the client pulls the latest server state. If you still see old data, go on. 1. Try a different client (browser vs Teams desktop vs mobile). Expected result: if the change appears in one client but not another, the problem is client-specific (cache or client version). If none show the change, the write may not have reached the server. 1. Update the client apps (Teams, Lists mobile, OneDrive sync client) to the latest supported version. Expected result: a client update fixes known sync bugs. [If updates are blocked](https://todayfixtech.com/microsoft-365-updates-features/) by policy, check with your admin. 1. Check whether updates are blocked by enterprise policy. ```text Windows > Settings > Update & Security (if device-managed, check Intune / Company Portal for update restrictions) ``` Settings path Expected result: if policy blocks updates, the admin must allow a newer build to resolve client bugs. If none of these restore expected behavior, move to deeper troubleshooting. ## Deeper troubleshooting steps if quick fixes fail Clear browser and Teams cache (safe, reversible) 1. Clear the browser cache for the SharePoint/Lists site or open a private window and test. ```text Browser > Settings > Privacy & security > Clear browsing data > Cached images and files ``` Settings path Expected result: cached pages or scripts no longer show stale data. If stale data remains, try the Teams cache. 1. Clear Teams cache (desktop). close Teams before you clear the cache. ```text %appdata%\Microsoft\Teams\Cache %appdata%\Microsoft\Teams\IndexedDB %appdata%\Microsoft\Teams\Local Storage ``` Settings path Delete files in those folders, then restart Teams. Expected result: Teams fetches fresh list data. If Teams still shows old items, continue. Reset OneDrive/SharePoint sync client or re-link the list (when you sync a library to Files in Teams) 1. If you use OneDrive to sync the underlying SharePoint document library, restart or reset the OneDrive client. ```powershell # There is no single universal PowerShell reset; use the UI: # Right-click OneDrive icon > Settings > Account > Unlink this PC > Sign in and re-add the site ``` PowerShell Expected result: the client re-downloads content and resolves local/remote differences. If files or list items still mismatch, check list customizations. Inspect custom columns, lookup fields and column formatting - Custom column types, complex lookup fields, or JSON column formatting can slow or break updates in non-browser clients. Temporarily switch to a simple view (standard columns) and test an edit. Expected result: if a simplified view syncs, a custom column or formatting is likely interfering. Check Power Automate flows and event receivers - Flows that update items immediately after save can create update conflicts. Temporarily disable suspicious flows and test. Expected result: disabling the flow removes conflicting immediate updates. If that fixes the issue, adjust the flow to avoid write loops. Conditional Access / Intune policies - Conditional access policies or device compliance rules can block background sync or access from mobile/desktop clients. Coordinate with your admin to verify device and app access policies. ```text Microsoft 365 admin center > Azure Active Directory > Security > Conditional Access ``` Settings path Expected result: if a policy is blocking token refresh, allowing the client or device compliance resolves the sync. If nothing helps: recreate the connection recreating or unlinking sync can remove local cached copies; ensure no unsynced changes exist before proceeding. 1. For a synced library, unlink and re-link the library from OneDrive or remove and re-add the Files tab in Teams. Expected result: a fresh sync normally resolves persistent cache corruption. If items remain missing, inspect list version history and audit logs as the next verification step. ## How to verify the sync is actually fixed and confirm no data was lost Verify from multiple clients 1. Edit a non-critical field on an item from the browser (SharePoint UI). 2. Immediately check the same item from Teams desktop and the Lists mobile app. Expected result: the change appears in all clients within a minute or two. If it does, the sync is working. Check version history and recycle bin - Use item version history to see whether the server recorded the edit. ```text List > Select item > Version history ``` Settings path Expected result: the new version with your change appears. If the edit is not in version history, the write did not reach the server. [Audit logs and Microsoft](https://todayfixtech.com/microsoft-365-tips-tricks/) 365 admin center - Admins can search audit logs for item update events to confirm replication. ```text Microsoft 365 compliance center > Audit > Search > Activities: "Updated list item" ``` Settings path Expected result: entries show which account made changes and when, confirming replication across services. Confirm full data integrity - Compare item counts and key field values between two clients after sync (browser vs mobile). If counts differ, check the list view filters and lookup field links. If items are missing 1. Check the site recycle bin for deleted items. ```text Site contents > Recycle bin ``` Settings path 1. If version history shows conflicting edits, restore the correct version from version history. ## Prevention and what to watch for next time Practical steps to reduce future sync breaks - Keep clients updated: ensure Teams, Lists mobile, and OneDrive are on supported builds so you get fixes for known sync bugs. - Avoid unsupported or very complex column types: large multi-lookup sets, heavy JSON column formatting, and certain third-party field types are more likely to cause client inconsistencies. - Watch list size and view thresholds: very large lists (many thousands of items) or views that return all columns can slow replication and cause timeouts; use indexed columns and filtered views. - Document flows and customizations: keep a short runbook of Power Automate flows, event receivers or scripts that write to the list so you can disable them quickly when troubleshooting. - Admin checks: routinely check Microsoft 365 service health and any conditional access/Intune policies that affect background access for Teams and mobile apps. What to watch for in daily use - Immediate conflicting updates from automated processes, persistent client cache after app updates, and failures in third-party integrations are common repeat offenders. When the issue recurs, capture a timestamp and the account that performed the edit to speed diagnostics. ## Conclusion If refresh, sign out/in, or switching clients doesn't fix the problem, clear client caches, inspect custom columns and flows, and check conditional access with your admin. After each change, verify from at least two clients and check version history or audit logs. If items are still missing or audit logs show no writes, involve your Microsoft 365 admin or open a support ticket with timestamps and affected accounts. ## Frequently Asked Questions ### Why do edits sometimes appear in the browser but not in Teams? The browser talks directly to the SharePoint service, while Teams and mobile apps use cached copies or intermediary services and separate tokens. If a client cache or token is stale, it can show older data until it refreshes. ### Can Power Automate flows cause items to not show up? Yes. Flows that update items immediately after a user edit can create rapid write conflicts. Temporarily disabling suspect flows is a valid troubleshooting step. ### What if a large list is slow to sync? Large lists or views that return many columns can timeout or be truncated for some clients. Use filtered views, index key columns and avoid heavy JSON formatting on frequently updated columns to improve reliability.