Skip to main content

Slow application performance when opening, saving or using the plan

Written by Charnjit Singh Dharival

The Orchestrate system is running slowly with many users have been complaining about the length of time to do imports and saving the plan.

Task planner responding slowly to searches for specific tasks.

Taking ages to open plan or save the plan, stuck with the not responding message.


  • If the overall application or using the plan is taking too long, the functionality has been enhanced in Orchestrate version 7.77.

  • If your plan is taking too long to open, the functionality has been enhanced in Orchestrate version 7.77 hotfix 10.

  • If saving the plan is taking too long, the functionality has been enhanced in Orchestrate version 7.80.

  • Orchestrate version 7.80 hotfix 10 contains enhancements to prevent transactions becoming uncommittable when another database operation would occur that is trying to use the same connection. This prevents blocking of transactions within the database.

  • Orchestrate version 7.80 hotfix 20 contains an enhancement to speed up full shuffling when planning works orders. This prevents new transactions to attempt using already-allocated connections, resulting in blocking.

  • An enhancement has been made to skip full shuffling when planning works orders. Unnecessary checks removed when recalculating KPIs and Plots. This enhancement will be part of Orchestrate version 7.81. This will improve plan and application performance significantly. Please upgrade to this version or above.

  • Orchestrate version 7.82 contains implementation of pagination for Order Planner and Task Planner; The Task Planner and Order Planner views now include pagination controls for improved performance with large datasets. Instead of loading all records at once, results are displayed in pages (default 25 per page) with options to choose 10, 25, 50, 100, 1,000, or All. Navigation buttons (Previous/Next and clickable page numbers) allow quick browsing through results. Sorting, searching, and filtering continue to work as before — pagination is applied after these operations. The statistics bar always shows the total count of all matching records. Minor performance improvement when selecting order(s) in Order Planner - Improved performance when selecting orders in the Order Planner. The selection operation is now faster, especially when working with plans containing a large number of tasks. Improved SFDC performance when processing deleted operations - Improved SFDC performance by eliminating unnecessary label processing for deleted and expired operations. Labels are no longer generated for operations marked as deleted or archived, and existing orphaned labels are cleaned up during the publish cycle. Completed operations remain visible in SFDC with their labels intact within the configured retention period. Faster ‘Build View for Order’ performance - Improved the performance of the "Build View for Order" feature. When viewing an order's resources on the Gantt chart, the display now updates more efficiently, resulting in a faster and smoother experience — especially for orders with many allocated resources. Additionally, obsolete resources are now correctly excluded from the view. Stability improvements and faster plan loading for large databases - Fixed a crash that occurred when opening plans with very deep task dependency chains. Improved plan loading performance with multiple optimizations across task relation processing, KPI calculation, resource synchronisation, and shift pattern assignment loading. Faster search window performance - Improved the performance of the database search feature. The search window now opens faster, particularly on larger databases, by using a more targeted query to retrieve column information and by reusing existing database connections instead of creating new ones each time. Faster plan loading for plans with secondary resource groups - Improved performance of secondary resource group synchronisation. Plan loading and resync operations involving secondary resource groups are now significantly faster, especially for plans with large numbers of tasks. Only changed data is synchronised instead of reloading all secondary resource groups on every sync. Improve Orchestrate Gantt Chart Performance - Improved Gantt Chart rendering performance when working with large plans (hundreds of resources, 100k+ tasks). The chart now skips rendering for resources that are scrolled out of view (above or below the visible area), and avoids drawing task labels when they would be too small to read. These changes reduce rendering time during scrolling and zooming, resulting in a smoother planning experience.

    o Viewport culling ensures only visible tasks are rendered, dramatically reducing draw workload:

    ▪ Draw reduction; Up to 99% fewer tasks that require rendering.

    ▪ Render speed; Average render duration dropped from ~475–969ms to ~100– 156ms, a 5–8× speed improvement.

    ▪ Scalability; Render cost is now proportional to visible tasks, not total dataset size, so the Gantt scales gracefully regardless of plan size.

    o Scrolling and zooming should feel significantly more responsive for large-scale plans.

    • Stability fixes and improvement


If the issue continues to occur, it is likely to be an environmental issue causing the SQL server to run slowly or network speed to run slowly e.g. missing Windows or Security updates.


Initial steps users can take to resolve this issue are (you may need to speak to their IT department for assistance):

  1. Enquire if any changes have be made to the SQL server prior to the system running slowly (New Antivirus/Firewall, changes to an existing Antivirus/Firewall. Windows update etc).

  2. Test if undoing any potential changes speeds up Orchestrate.

  3. Restart the SQL Server Orchestrate Service on the SQL server.

  4. Check the Network speed.

  5. Archive all completed tasks or within a specific date range.

  6. Upgrade to the latest version of Orchestrate

  7. Delete old plans from Plan Explorer sub-directories e.g. Saved Plans (select file, plan explorer).

  8. If you use the Demand Planner to look at the Stock Plot, then change the Look Ahead Day to something smaller (like 30 days) which will make the plan load a lot faster.

  9. Create views with less resources in them, otherwise Orchestrate needs to load everything into memory (hide some of the resources if they aren't necessarily required to show).

  10. Move Orchestrate Virtual Machine server to SSD hard drives.

  11. Install the full SQL server Engine and not the Express Edition.

If you are still having performance issues, please raise a new case online and reference the title of this article.

Did this answer your question?