Project Planner 3 Slowing down

Irfan Hossain 20 Reputation points
2026-11-17T08:21:59.1366667+00:00

Experiencing slow performance while using the Project Planner 3 app.

The affected project contains more than 50,000 assignments and is the only project exhibiting performance degradation. Smaller projects operate normally.

Microsoft 365 and Office | Project | For business | Other
0 comments No comments

2 answers

Sort by: Oldest
  1. AI answer

    2026-11-17T08:23:53.2933333+00:00

    “Planner and Project Plan 3” is a license rather than a single application, so identify whether the affected schedule is a Planner premium plan, a Project desktop .mpp file, or a Project Server/PWA project before applying product-specific remediation.^1^

    If it opens in Planner for the web or Planner in Teams

    This is now the normal location for former Project for the web plans. Project for the web has been retired and its plans are available through Planner.^1^

    Microsoft documents these premium-plan limits:

    • 3,000 tasks per project
    • 300 resources per project
    • 20 resources assigned to one task
    • 2,000 successor links per project

    The published table does not specify a separate maximum for total assignments.^2^ Therefore, 50,000 assignments cannot be declared unsupported from that number alone, but it is a plausible workload factor because only this unusually large plan is affected.

    Perform a controlled test:

    1. Record the task, resource, and assignment counts.
    2. Create a copy or administrator-approved backup of the plan. Do not test by deleting production data.
    3. In the copy, remove a defined block—such as completed work before a chosen date—or approximately 25% of assignments.
    4. Time the same operations before and after reduction:
      • Opening the plan
      • Switching Grid, Board, and Timeline views
      • Editing and saving a task
      • Assigning or removing a resource
    5. Repeat with a second reduction if necessary.

    If performance improves in proportion to the assignment reduction, reduce the production workload by archiving completed work or separating future phases into additional plans. Treat this as a workload mitigation, not a documented Microsoft assignment-limit fix.

    If the copied plan remains slow, have a Microsoft 365 administrator open Microsoft 365 admin center → Help & support → New service request. Include:

    • The Planner plan URL
    • Task, resource, and assignment counts
    • Exact operations and timings
    • Browser versus Teams comparison
    • Reproduction timestamps with time zone
    • Affected user IDs and tenant ID, submitted only in the secure support case
    • Any correlation or request IDs shown by the client

    Support will need to inspect service telemetry or the affected plan’s backend state.

    If it is a Project desktop .mpp file

    Project desktop supports up to 400,000 tasks and 700,000 resources, but Microsoft states that actual limits and performance depend on the computer configuration and that memory errors can occur before a published maximum is reached.^3^

    The cited specifications do not provide a specific remedy or performance threshold for 50,000 assignments. Use the same copy-based reduction test above, and record:

    • Project version and build
    • 32-bit or 64-bit Office
    • File size
    • Local drive versus network/SharePoint storage
    • Time required to open, recalculate, save, and close

    If reduction does not isolate the issue, open a Microsoft 365 support request and attach a sanitized copy if organizational policy permits.

    If it is Project Server/PWA

    Project Online retired on September 30, 2026; if the URL is a former Project Online PWA site, contact the tenant’s migration administrator or Microsoft support rather than making legacy configuration changes.^4^

    For a supported Project Server/PWA deployment, apply these conditional changes:

    • Slow publishing or Project Detail Page transitions, with SharePoint Task List synchronization enabled: An administrator should open Project Web App Settings → Enterprise Project Types → select the affected EPT → Synchronize, disable Sync SharePoint Tasks Lists, and retest. Microsoft describes this synchronization as intended for small plans and recommends it only for projects with fewer than 250 tasks.^4^
    • Slowdown during OData or report refreshes: Avoid full “refresh everything” loads, run refreshes after hours, and constrain queries with $filter and $select. Microsoft notes that large unfiltered requests add latency and can degrade PWA operations.^4^

    References

    1. Frequently asked questions about Microsoft Planner | Microsoft Support
    2. Project for the web limits and boundaries
    3. Specifications for Microsoft Project | Microsoft Support
    4. Tune Project Online performance
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

  2. Darren Bruce 2,860 Reputation points Independent Advisor
    2026-11-17T08:51:56.42+00:00

    Dear Irfan Hossain,

    Based on your description, the performance degradation appears to be isolated to a single Project Planner 3 project that contains more than 50,000 assignments, while other smaller projects continue to function normally. This behavior may indicate that the issue is related to the size and complexity of the project rather than a general service problem.

    Here are a few recommendations that may help:

    • Try opening the project using an InPrivate/Incognito browser session to rule out browser cache or extension-related issues.
    • Check whether the performance issue occurs for all users who access the same project or only specific users.
    • Review the project structure and determine whether some assignments, tasks, or resources can be archived, split into multiple projects, or otherwise reduced in volume. Projects with very large numbers of assignments can experience longer load and processing times.
    • Verify whether the issue occurs in different browsers (Microsoft Edge, Google Chrome, etc.).
    • Monitor network requests through the browser's Developer Tools (F12) while loading the project to identify potential delays, timeouts, or failed requests.

    I hope it helps, feel free to reach out if you have any other questions.

    Was this answer helpful?


Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.