July 9, 2025

• Web: 1.1.0
• CLI: 3.3.0
• Cloud: 2.7.0

New features

Maximum number of deployment attempts

The maximum number of deployments that OrgFlow will attempt before failing can now be specified for flow out and flow merge jobs.

Previously this was hard-coded to 5 attempts, which remains the default.

For OrgFlow Web, a new input field has been added to the flow out and flow merge dialogs; for OrgFlow CLI the new --maxAttempts option has been added to the env:flowout and env:flowmerge commmands.

Purge on delete

The purge on delete deployment option can now be specified for flow out and flow merge jobs. Purge on delete bypasses Salesforce's recycle bin and makes deleted metadata components immediately eligible for deletion in the org.

Previously this was hard-coded to Auto which means to purge on delete only when deploying to a sandbox. The new configurable option defaults to Never which instead optimizes for safety and does not purge on delete regardless of target org type.

For OrgFlow Web, new radio buttons have been added to the flow out and flow merge dialogs; for OrgFlow CLI the new --purgeOnDelete option has been added to the env:flowout and env:flowmerge commmands.

Improvements

Fixes

• Fixes an issue with inbound flow where excluded composite components could be incorrectly deleted in some circumstances
• Fixes an issue where a stack's baseline API version would only be kept up to date if the effective version selection mode for at least one environment in the stack was baseline
• Web: Fixes an issue where current billing period would be visualized incorrectly on the billing and usage page