Deployment adds orders to the Daily Plan instead of updating orders

Current Situation

• If a workflow is renamed and is deployed then
  • existing orders for the workflow are not removed from the Daily Plan
  • new orders are added to the Daily Plan
• As a result we find double execution of workflows, see linked SourceForge thread.

Desired Behavior

• Calls to the /inventory/deployment/deploy API must include a delete object and a store object to reflect that the underlying workflow was renamed.

Workaround

• Instead of deploying the workflow, users can release the schedule. Due to built-in dependency management when renaming a workflow automatically both the workflow will be deployed and the schedule will be released from whichever operation is performed first.
• The error is triggered when initiating the deploy/release operation by deploying the workflow. The error is not triggered when initiating the operation from releasing the schedule.