Overview
This issue occurs because the database connection timeout was not previously applied to plan actions such as copying, saving, or deleting. Several improvements and fixes have been introduced across Orchestrate versions to address this behavior.
Version updates and improvements
Orchestrate 7.62
Added a code enhancement to correctly apply the database connection timeout when copying, saving, or deleting a plan.Orchestrate 7.75 (Hotfix 30)
Further enhancements were introduced to improve plan processing and stability during save operations.Orchestrate 7.76 (Hotfix 30)
Introduced a new system parameter called Prevent Simultaneous Actions.
This prevents multiple users from saving the same plan at the same time by placing save requests into a queue.Orchestrate 7.77
Improved plan saving performance by refactoring the logic used to bulk‑insert updated tasks.Orchestrate 7.78
Enhanced plan saving when archiving completed tasks and resolved timeout issues caused by saving attributes on a high volume of orders.
What we recommend
Upgrade to Orchestrate version 7.78 or later, which contains the most comprehensive fixes for this issue.
Need further help?
If the issue continues after upgrading, contact our support team via chat, and if you haven't done so, include the error you are seeing so that we can assist further.