Microsoft Planner not syncing: fix tasks that won’t update

If Microsoft Planner isn’t syncing, the problem is usually a stale view, a sign-in mix-up, or a delay between Teams, the web app, and your phone. Start by refreshing, checking that you’re in the right account and plan, then signing out and back in. If the same task still won’t update everywhere after that, it may be a permissions change or a Microsoft service issue rather than something on your device.

What ‘not syncing’ usually looks like

Most Planner sync problems show up in a few familiar ways. You change a task on the web, but Teams still shows the old status. A task moves buckets on your phone, then jumps back after you refresh. Sometimes a task seems to disappear for a while and then comes back later, which usually points to delayed propagation rather than a true loss of data.

The key clue is whether the problem is consistent across every place you open Planner. If only one app is stale, you are probably dealing with cache, sign-in, or app refresh issues. If every device shows different information for the same plan, or one device is missing the plan entirely, that points more toward account, permissions, or service-side trouble.

The symptom to look for

Planner shows different task data in Teams, the web app, and the mobile app.

This usually shows up right after you change a task, move it, or mark it complete. If one view updates and another still shows the old version after a refresh, the issue is still active. If the mismatch only appears in one place, that surface is probably showing stale cache or a stale sign-in session.

Before you start

These fixes apply to the normal Planner experience in Microsoft 365, including Planner in Teams, the web app, and the mobile app. You do not need administrator rights for the first checks, and none of the steps below require a restart or any risky cleanup.

Start with two safe checks before you change anything else:

• Make sure you are looking at the correct Microsoft account.
• Make sure you opened the right plan, not a similar one with the same name.

These fixes help when the issue is local to your session, app cache, or connection. They will not fix a plan that you no longer have permission to see, a tenant-wide outage, or a plan that has been moved or removed by someone with admin access.

Start with the quickest safe fixes

Begin in the place where you first noticed the problem, then compare it with another place like the web or Teams. The goal is to force a clean refresh before you try anything more disruptive.

1. Refresh Planner.

If you are using Planner in a browser or in Teams, reload the page or switch away from the plan and back again.

The plan reloads and recent task changes appear after a moment.

If the data updates now, the issue was just a stale view. If nothing changes, move on.

2. Confirm the account and plan.

Check the profile or account switcher and verify you are signed into the Microsoft account that owns access to the plan. Then open the exact plan, not a different one from the same team or group.

Profile or account menu > switch to the correct Microsoft account

If the wrong account was selected, signing into the correct one should make the missing tasks appear. If the right account was already in use, continue.

3. Sign out and back in.

Sign out of Planner, Teams, or the Microsoft 365 session you are using, then sign in again. This clears a lot of temporary session problems without changing your data.

Profile or account menu > Sign out > sign back in

Planner opens normally after sign-in and recent changes match the other device.

If the problem remains, the session was not the only issue.

4. Clear cached data for the app or browser.

If you use Planner in a browser, clear site data for Microsoft 365 or try a private window. If you use the Teams desktop app or the mobile app, clear the app cache through the app’s own settings or your device settings, then open Planner again.

Browser settings > site data / cached data for Microsoft 365

Planner reloads with current task data instead of showing an old copy.

If clearing cache fixes it once but the problem returns often, the cache is getting stuck again. That usually means an app update issue, a browser profile problem, or a sign-in/session conflict rather than a Planner data problem.

How to check that syncing is working again

Use a simple test that you can watch from more than one place. Pick one task in the affected plan and change something obvious, such as the title, checklist, bucket, or completion status. Then open the same plan in another surface, such as Teams if you changed it in the web app, or the mobile app if you changed it on desktop.

A working sync usually looks like this:

• The task update appears in the second place after a short delay.
• Refreshing the second place does not bring back the old version.
• The same change still shows after you sign out and back in.

If the update appears in one view but not another, the issue is still active. If the change reaches every place you check, sync is working again and you can go back to normal use. If you want to be extra sure, make one more harmless change, then reverse it, and confirm both states show up everywhere.

Why Planner gets out of sync in the first place

The most common cause is not a true sync failure but a delay in how quickly updates move between apps. Planner in Teams, the web app, and the mobile app do not always redraw at the same moment, so one surface can lag behind even when the data is fine.

A few other causes are easy to miss:

• Offline or weak connectivity while you edited a task.
• Stale browser or app cache showing an old version of the plan.
• An outdated Teams, browser, or mobile app build.
• Signing into the wrong Microsoft account in one place.
• Using Planner in Teams vs the web app, where one view can lag or keep older session data longer than the other.
• Permissions or membership changes that removed your access to the plan or its underlying Microsoft 365 group.
• A plan that was moved, renamed, or reconfigured by someone else in the tenant.

If a permission changed, you might still see the plan in one app briefly while another app refreshes and realizes you no longer have access. That can feel like syncing broke, but the real issue is access control. The same thing can happen if the plan is tied to a group or team and membership changes have not fully propagated yet.

When to escalate to Microsoft or your admin

If the problem affects more than one device and survives refresh, sign-out, cache clearing, and a correct account check, it is time to escalate. A service-wide problem is more likely when several people in the same tenant see the same stale data or when Planner is failing across Teams and the web at the same time.

Ask your admin to check three things:

• Microsoft 365 service health for Planner and Teams.
• The permissions on the plan, team, or Microsoft 365 group.
• Whether your account and the affected users still have the right licenses and membership.

If your admin sees a known incident, that usually explains the delay and there is nothing local to fix. If service health looks normal, the next most likely issue is a permissions or tenant configuration change. In that case, ask them to confirm that the plan is still attached to the right group, that membership is intact, and that no policy change is blocking access in one of the apps.

Conclusion

If Planner still will not update after those checks, stop changing things on your side and compare what each app shows with a known good browser session or another account that has access. At that point, the fastest next step is usually an admin check for permissions or a Microsoft service health issue. Once the underlying access or service problem is fixed, Planner usually catches up on its own.

Frequently Asked Questions

Why does Planner update in Teams but not in the web app?

That usually means one view is holding stale cache or a stale sign-in session. Refresh, sign out and back in, then compare the same plan in a private browser window or another browser profile.

Can a permission change make Planner look like it is not syncing?

Yes. If your access to the plan, team, or Microsoft 365 group changed, one app may keep showing old data for a while before it realizes you no longer have the same permissions. That can look like a sync problem even when the real issue is access.

How do I know if Microsoft is having a Planner outage?

If multiple users are seeing the same delay or missing updates across different devices and apps, that is a strong sign. Your admin should check Microsoft 365 service health for Planner and Teams.