Microsoft Planner not updating: fix stuck task changes

If Microsoft Planner isn’t updating, the change usually saved in one place but not everywhere yet, or one view is showing stale cached data. Start with a refresh, then sign out and back in, and check Microsoft service health before you clear cache or switch devices. In many cases, the task is correct in the source plan and only Teams, the browser, or the phone app is out of date.

What you’re likely seeing when Planner stops updating

The usual symptom is that a task change appears in one place but not another. For example, you assign a task on your desktop, but your phone still shows the old assignee. Or you add a due date, checklist item, comment, or status change, and it looks like it never took effect until later, if it shows up at all.

Sometimes only one plan looks stale, while other plans update normally. Other times the task card changes in the Planner board, but the details pane, Teams tab, or mobile app keeps showing an older version. That usually points to a display or sync delay rather than a lost edit.

The changes people notice most often are:

• assignments
• due dates
• checklist items
• comments
• progress or status changes

If those updates lag, the first job is to find out whether the task actually saved or whether you’re only looking at an old copy of the plan.

Before you start

This applies to Microsoft Planner in the web app, Teams, desktop app, and mobile app. You do not need administrator rights for the basic checks below, but checking Microsoft 365 service health does require admin access in the Microsoft 365 admin center.

No restart or backup is needed for the first checks. Before you make deeper changes, try these safe checks first:

• refresh the page or reopen the app
• sign out and sign back in
• check whether Microsoft has a service issue

If the problem only happens in one browser, one device, or one team plan, that detail is useful. It usually tells you where to look next.

Symptom

Planner shows an older version of a task in one view, but the change appears somewhere else or appears later.

This usually shows up right after you edit a task, switch between Teams and the web app, open the plan on your phone, or return to a shared team plan after a while. The exact message varies because Planner usually does not show a single standard error for this problem.

When this is a Planner issue and when it’s really Teams, the browser, or your account

Start by separating the source plan from the place where you’re viewing it. If the task is stale only in Teams, the issue is often Teams caching or Teams app sync, not Planner itself. If it’s stale in one browser but correct in another, that usually points to browser cache, extensions, or stored site data. If it’s wrong on one device but correct on another, the device app or local cache is the likely culprit.

A Microsoft service delay is more likely when:

• multiple people see the same lag
• several plans are affected at once
• the same issue happens across phone, desktop, and browser

A permission issue is more likely when you can open the plan but can’t reliably change certain fields, or your changes vanish because you don’t have the right access to that plan. A plan-specific glitch is more likely when one shared plan misbehaves while other plans in the same account work normally.

Before you change settings, check whether this is just one view being stale or whether the change truly failed to save in the plan itself.

The quickest fixes that usually get Planner updating again

Start with the least disruptive steps first. These are safe and usually enough when the problem is just stale data.

1. Refresh the page or reopen the app.

The task list reloads and recent changes appear.

If you’re in Teams, close the tab or switch away from the plan and open it again. On mobile, force-close the app and reopen it. If the update appears after that, the problem was a temporary display delay.

2. Sign out and sign back in.

You return to the plan with current data.

This helps when your session token is stale. If the update shows up after a fresh sign-in, your account session was the issue.

3. Check Microsoft service health.

Microsoft 365 admin center > Health > Service health

If you don’t have admin access, ask someone who does to check. A service incident can cause updates to lag or fail across multiple users. If there’s an active issue, the safest move is usually to wait rather than keep changing settings.

4. Clear the browser cache for the site, or try a private window.

If the problem only happens in one browser, this is a strong clue that cached data or a browser extension is involved.

Browser settings > Privacy and security > Clear browsing data

Clear cached files and site data for Microsoft 365 or try a private/incognito window first. If the plan updates there, your normal browser profile is holding stale data.

5. Try a different browser or device.

The same plan shows the current task state.

If Planner works elsewhere, the original browser or device is the problem. If it fails everywhere, you’re likely dealing with a service issue, a permission problem, or a plan-level sync delay.

How to confirm the change actually saved

The best way to tell a real save failure from a display delay is to check the task from the source plan, not just from the place where you made the edit. Open the same plan in the web app, then open the task card and look at the assigned person, due date, checklist, comments, and progress state there.

If the change is visible in the source plan but not in Teams or on your phone, the save probably worked and the other view is stale. If the change is missing in the source plan too, the edit may not have saved, or you may have lost connection while making it.

A useful check is to ask a teammate who has access to the same plan to open it and confirm what they see. If they can see the update and you cannot, that points to your device, browser, or app session. If nobody can see it, the change likely did not stick.

One more clue: if you edit a task and the page appears to accept the change, but the value reverts after a refresh, that usually means the update didn’t save to the shared plan.

Why the same plan can update on one device but not another

This usually comes down to four things: cached data, app version differences, offline edits, or access limits.

Stale cached data is the most common reason. One browser or device keeps showing an older version of the plan even though the server already has the new data. A refresh fixes it sometimes, but if not, the stored site data may need to be cleared.

App version differences can matter too. If one device uses an older Planner or Teams app, it may not handle refreshes or sync the same way as a newer version.

Offline edits can also cause confusion. If you changed a task while the app was offline or the connection was unstable, the change may queue up and sync later, or it may fail quietly and leave you looking at the old state.

Shared-plan permissions can create a more limited symptom. You might still open the plan, but not every field behaves the same way if your access is restricted. That can show up as changes not sticking, missing comments, or task details that won’t refresh correctly.

If the problem only happens in one team plan, compare it with another plan in the same account. If the other plan updates normally, the issue is probably specific to that shared plan or its cached view, not to your whole account.

How to avoid the problem coming back

Keep the desktop app, mobile app, browser, and Teams client updated so you’re not mixing very different versions. If you use Planner in Teams a lot, try to stick with one main browser or app for day-to-day work, because switching between several clients can make stale views harder to spot.

Avoid long editing sessions while offline or on an unstable connection. If you know your network is flaky, wait until you have a steady connection before making a batch of task changes.

When only one plan is misbehaving, save your work, then check it from another view before assuming the edit failed. If several people are seeing the same lag, it’s usually better to wait for Microsoft to recover the service than to keep changing settings on every device.

If the same browser keeps showing stale data, clear its site data once and then test again before making deeper changes.

Conclusion

If Planner still isn’t updating after a refresh, sign-in reset, and a service-health check, test the same plan in another browser or device. That usually tells you quickly whether you’re dealing with a stale cache, a Teams-only view, or a broader Microsoft issue.

Frequently Asked Questions

Why does Microsoft Planner show old data in Teams but not in the browser?

That usually means Teams is showing a cached or delayed view of the plan. If the browser shows the new value, the Planner data likely saved and Teams just hasn’t refreshed cleanly yet.

Why did my Planner task change disappear after refresh?

If the change vanishes after reload, it may not have saved to the shared plan. A brief connection drop, a sync delay, or a permission issue can cause that.

What changes in Planner are most likely to lag?

Assignments, due dates, checklist items, comments, and progress or status updates are the ones people usually notice first when sync is delayed.