Microsoft Planner stuck — diagnose & fix a frozen plan fast

If a Microsoft Planner plan is frozen, shows a continuous spinner, or won’t save edits, start with quick client-side checks: refresh the page, sign out and back in, or open the plan in an incognito window or another browser. These actions fix most loading and cache-related problems; if they don’t, follow the deeper steps below to isolate network, Teams, permission, or service-side causes. Collect the listed evidence before escalating to IT or Microsoft Support.

Is Planner actually stuck or is it one of these specific symptoms?

Identify the exact symptom before applying fixes; different symptoms have different causes and fixes.

Infinite loading spinner that never completes.
Page or UI appears frozen: clicks and buttons don’t respond.
Can’t create, edit, or move tasks: UI accepts input but changes don’t persist.
Task updates or comments don’t sync between collaborators.

When it appears

• Right after sign-in or page load: suggests client-side loading, auth token, or service throttling.
• Only inside the Teams desktop app but works on planner.microsoft.com: suggests Teams integration or client cache issue.
• For multiple users at once: more likely a tenant or Microsoft service problem.

Why this matters

• An infinite spinner or frozen UI usually calls for client-side refreshes, cache clears, or switching between browser and Teams before doing anything invasive.
• Create/edit failures point to permission, tenant configuration, or blocked network requests.
• Sync problems can be service-side or caused by inconsistent caching between clients.

Identifying the symptom saves time and avoids unnecessary steps.

Could this be my environment or is it a wider outage?

Applicability: which products and privileges this applies to, quick safe checks to do first.

• Product/versions: Planner in a browser, Planner inside Microsoft Teams (desktop and web), planner.microsoft.com.
• Privileges: no admin rights required for the initial checks. Tenant admin rights are required to view full Service Health details in the Microsoft 365 admin center.
• Restart/backup: no restart or backup is required for the initial checks. The steps below are reversible and non-destructive.

Safe checks to do first

1. Ask a colleague to open the same plan or open the plan from another device.
2. Try planner.microsoft.com in a private/incognito browser window.

Quick checks to decide scope

1. If you have tenant admin access, check Microsoft 365 Service Health in the Microsoft 365 admin center.
2. Check a public outage tracker such as DownDetector for concurrent reports.
3. Confirm whether multiple users in your tenant see the same symptom.

What each result suggests

• Only you affected: likely client-side (browser cache, extensions, Teams cache, local network).
• Several users in your tenant: possible tenant configuration, conditional access, or admin settings.
• Many public reports or Service Health flagged: Microsoft service incident — follow Microsoft guidance or have your tenant admin open a support ticket.

If Service Health is unclear and multiple users are affected, escalate to your tenant admin with times and affected users so they can open a Microsoft support case.

Quick fixes to try right now (less than 5 minutes)

Try these low-risk, non-destructive actions in order. Stop as soon as Planner works.

1. Refresh the page.
2. Sign out of your Office 365 account and sign back in.
3. Open the plan in a private/incognito window to bypass cached state and many extensions.
4. Try a different browser or switch between Planner in Teams and planner.microsoft.com.
5. Temporarily disable browser extensions, especially ad-blockers or privacy tools, then reload.

Where to act and privileges

• Browser or Teams client: no special privileges required.

Expected results and next step

• If a quick fix makes Planner usable and the change persists for a few minutes and for collaborators, you’re done.
• If none of these steps help, proceed to the deeper troubleshooting steps below.

If quick fixes don’t work: deeper troubleshooting steps

Work through these reversible steps. Stop and verify after each.

1. Clear browser cache and cookies for the site.

Chrome: Settings > Privacy and security > Clear browsing data > Cookies and other site data + Cached images and files
Edge: Settings > Privacy, search, and services > Clear browsing data
Firefox: Settings > Privacy & Security > Cookies and Site Data > Clear Data

Expected result: planner pages load fresh and the spinner or stale content disappears. If not, browser-level caching wasn't the cause.

2. Update or reinstall the Teams desktop app.

• Where to act: Teams desktop app. Privilege: normal user install/update rights.

Restart Teams after updating.

Expected result: the plan loads in Teams. If web works but Teams does not, the Teams client cache or an integration bug is likely.

3. Check network, proxy, or firewall settings.

• Where to act: local network or corporate firewall/proxy. Privilege: may require IT help.

Ask IT to verify that Microsoft 365 and Planner endpoints are allowed by proxy/firewall and that conditional access policies are not blocking access.

Expected result: allowing required endpoints lets Planner communicate with Microsoft services. If it doesn't, collect network traces for escalation.

4. Disable all browser extensions and reload.

• Where to act: browser extensions menu. Privilege: none.

Expected result: if disabling fixes Planner, re-enable extensions one at a time to find the conflict. If disabling all doesn’t help, extensions aren't the issue.

5. Verify Planner permissions and plan membership.

• Where to act: Planner UI or Microsoft 365 admin center (Groups/Teams membership). Privilege: plan owner or admin required to change membership.

Steps:

1. Open the plan’s Group or Team and confirm your account is a member.
2. Confirm you are not a guest with restricted rights if you need create/edit permissions.

Expected result: correct membership and permissions restore create/edit behavior. If membership is correct but the problem persists, check conditional access or tenant-level restrictions.

6. Isolate Teams integration problems by opening the plan directly in the Planner web app.

Steps:

1. Open a browser and go to planner.microsoft.com and sign in.
2. Open the same plan. If the plan works in the browser but not in Teams, clear the Teams client cache.

Recreate a cached Teams view (safe step)

1. Sign out of the Teams desktop app.
2. Close Teams completely.
3. Sign in again and open the plan.

Expected result: Teams reloads the plan without stale cache. If the problem returns, clear Teams cache per your organization’s instructions or contact IT.

Don’t delete the Microsoft 365 Group backing a plan or reset user accounts without IT approval; that can delete plan data.

How to confirm Planner is fixed and avoid false positives

Verify the fix with reproducible checks.

1. Create a test task in the plan.
2. Edit the task title and description, add a comment, then move it between two buckets.
3. Ask a colleague to confirm they see the new task and your edits.
4. Refresh the page and open the plan in an incognito window and in the Teams client to confirm consistency.

Test task appears for you immediately and after a page reload.
Your colleague sees the task and edits within a short period.
Moving the task between buckets works and persists.

If changes appear locally but not for others, or revert after a short time, the problem may be a sync or service-side issue — collect the evidence below and escalate. Monitor for a few minutes to ensure changes persist.

When to escalate to your IT admin or Microsoft Support and what evidence to collect

Escalate when multiple users are affected, you see a Service Health incident, or the problem persists after troubleshooting. Provide clear evidence to speed resolution.

What to collect

• Screenshots showing the spinner, error messages, or frozen UI with timestamps.
• Exact times when the issue started and when you reproduced it.
• A list of affected users and whether they are internal or external to your tenant.
• Browser name and version, or Teams desktop app version. Include OS version.
• Steps you tried and their results (refresh, incognito, different browser, Teams vs web).
• Service Health status at the time (screenshot or note) and any DownDetector entries if relevant.
• Network traces or browser console logs if IT requests them; obtain capture instructions from IT first.
• The Microsoft 365 Group or Team name that owns the plan and the plan name.

Escalation path

• Single-user issue: contact local IT support; they can check conditional access and device configuration.
• Multiple users in the tenant: tenant admin should open a Microsoft support ticket and include Service Health checks and user impact details.
• Confirmed Microsoft service incident: follow guidance in the Microsoft 365 admin center and monitor the incident; tenant admins can request more detail from Microsoft.

Provide the collected evidence to your IT admin or Microsoft Support so they can reproduce and prioritize the issue.

Conclusion

If a quick refresh or switching clients fixes Planner, stop there. If not, follow the deeper steps, verify with a test task and a colleague, and collect the diagnostic details listed above before escalating.

Frequently Asked Questions

Why does Planner work in my browser but not in the Teams desktop app?

The Teams desktop app caches web views separately from the browser. If Planner works on planner.microsoft.com but not in Teams, sign out of Teams, close it completely, and sign in again. If that doesn’t help, update or reinstall Teams and check for Teams-specific policy restrictions from your tenant admin.

Can permissions cause Planner to appear stuck?

Yes. If you aren’t a member of the Microsoft 365 Group or Team that owns the plan, or you’re a guest with limited rights, create and edit operations can fail or appear to do nothing. Confirm plan membership and your role; a plan owner or tenant admin can change membership or guest access settings.