After the plan is saved and refreshed, the SFDC Publish To takes a long time to complete.
Solution 1
Please check and action the following:
With multi user planning and then saving the publish to SFDC could be queuing/skipping as other users are also saving the plan at the same time.
Check is you have a series of old plans with a lot of tasks. If so, delete some of these old saved plans.
Archive completed tasks.
Note: Even though publishing to SFDC is still running, Orchestrate is still responsive, so you can continue with what you are doing on the plan.
Solution 2
Notable enhanced and fixed have been devised to improve SFDCPublishTo performance:-
Since SFDC version 1.8.0: Improve SFDC messages in Multi User Environment
Orchestrate version 7.82: 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.
Orchestrate version 7.83: Chat messages added before a plan save now sync; chat added to tasks that did not yet exist in the database is picked up and pushed to SFDC after the plan is saved.
Saving the plan deselects the task after publishing to SFDC is completed; Fixed an issue where saving a plan would cause the currently selected task to become deselected when the database was linked to SFDC. The selected task is now preserved after saving.
Plan deletion and Save button issues in plan management; Fixed two issues in plan management: Plan deletion now properly cleans up current plan references, preventing stale entries in the system. The Save button on newly created plans now saves directly instead of incorrectly opening the Save Plan dialog; Save As continues to show the dialog as before.
Unsaved changes lost when a plan save fails; Fixed an issue where unsaved scheduling changes could be lost if a plan save operation failed. Previously, the application would reload data from the server after a failed save, discarding any task movements or edits made since the last successful save. The application now preserves all unsaved changes when a save fails, allowing users to retry without losing their work.
Plan save failing when tasks are modified by another user simultaneously; Fixed an issue where saving a plan could fail when another user simultaneously archived or unplanned tasks. The save operation now handles this concurrent editing scenario gracefully instead of rolling back all changes.
Please upgrade to Orchestrate version 7.83 or above.