August 7, 2025

• CLI: 3.4.1
• Cloud: 2.7.3

Improvements

We discovered a bug in the Salesforce metadata API where the API name of a component that failed to delete was sometimes reported as destructiveChanges.xml instead of the name of the component. This prevented us from tracking the failure state of that component, which in turn caused OrgFlow to repeatedly retry the deployment until the max number of attempts was reached. This release introduces a workaround that identifies the incorrect responses from the metadata API and transforms them to the correct values early in the process.