Changelog
December 22, 2025
- Web: 1.3.9
- CLI: 3.5.9
- Cloud: 2.9.12
New features
- Cloud: Free workspaces are now automatically disabled (scheduled jobs will not run) after 14 days of inactivity, and permanently deleted after 60 days of inactivity. Activity is reset whenever a user interacts with the workspace in OrgFlow Web.
Improvements
- Web: Improves error details in cases where there are problems signing in to a workspace
Fixes
- Web: Fixes an issue where managed worker jobs would sometimes spend an unreasonably long time in queue before running
- Fixes a recent regression that sometimes made CLI commands and managed worker jobs fail when Salesforce access tokens expire
December 12, 2025
- Web: 1.3.8
- CLI: 3.5.8
- Cloud: 2.9.11
Improvements
- Managed worker jobs and CLI commands now respond faster to cancellation requests
- CLI: Significantly improves performance and resource efficiency
December 4, 2025
- CLI: 3.5.7
- Cloud: 2.9.10
Fixes
- Fixes issue where sandbox environments could not be created if the sandbox did not already exist
December 3, 2025
- Web: 1.3.7
- CLI: 3.5.6
- Cloud: 2.9.9
Improvements
- Removes restrictions for deleting stacks and workspaces
- Improves memory efficiency across all systems
November 27, 2025
- Web: 1.3.6
- CLI: 3.5.5
- Cloud: 2.9.8
New features
- Web: Adds linked environment names in job titles
- Web: Web application and managed worker jobs now use the OAuth Username-Password Flow instead of SOAP API
login()to authenticate to Salesforce when using stored credentials. SOAP APIlogin()is not available in API versions 65.0 and later, and will be removed also from earlier API versions in the Summer '27 release (see this Salesforce Help article for more information). OrgFlow CLI still continues to use SOAP APIlogin()by default for now.
Improvements
- Web: Improves focus management, usability and accessibility of environment filter pickers and other pickers
- Upgraded underlying runtime to .NET 10 across all systems for improved performance
Fixes
- Fixes an issue where schedules could sometimes try to start jobs for environments that were not yet initialized
- Fixes an issue where progress data would not appear for jobs that had spent an unusually long time in pending status
November 17, 2025
- Web: 1.3.5
November 7, 2025
- Web: 1.3.4
- CLI: 3.5.4
- Cloud: 2.9.5
Fixes
- Fixes an issue where added/deleted nested components inside added/deleted standard or packaged composite components would be incorrectly omitted from deployments
- Fixes incorrect/inconsistent diff counts in deployment review and results
October 13, 2025
- CLI: 3.5.3
- Cloud: 2.9.4
October 10, 2025
- Web: 1.3.1
- Cloud: 2.9.3
Improvements
- Web: Adds ability to manage repository contributors for managed repos
- Web: Adds links to open Salesforce code in an online IDE for supported repositories
- Web: Improves device code flow user interface
September 30, 2025
- Web: 1.3.0
- CLI: 3.5.2
- Cloud: 2.9.2
New features
- This release delivers on our #1 requested feature: selective deployment! You now have the option to deploy only a selected subset of detected changes, while leaving the rest for later.
- We also completely overhauled the deployment review experience in this release, so that you can now tell new changes from prior, get a clearer and more detailed summary of changes, better understand standard/package metadata and clobber — and much more.
September 2, 2025
- Web: 1.2.1
- Cloud: 2.8.1
August 24, 2025
- Web: 1.2.0
- Cloud: 2.8.0
New features
- This release adds managed repositories to OrgFlow! 🎉 Don't want to bother with setting up a Git repository for your Salesforce metadata? Let OrgFlow create and manage a GitHub repository for you. If you want, we'll add you as a contributor.
Improvements
- Web: A new onboarding experience makes it easier than ever to get up and running with OrgFlow.
August 13, 2025
- CLI: 3.4.2
- Cloud: 2.7.4
Fixes
- Fixes an issue where processes might incorrectly fail when acquiring exclusive leases on environments.
- Web: Fixes an issue where users with an access level lower than Administrator were not permitted to delete the Git branch or Salesforce sandbox along with the OrgFlow environment itself, even when they were the environment owner.
- Web: Fixes an issue where any flow jobs in a stack would appear to be stuck if one or more environments in the stack were still being created (uninitialized) because stack baseline API version determination would fail and retry indefinitely. Baseline API version is now determined only based on fully initialized environments.
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.
August 2, 2025
- Web: 1.1.2
- CLI: 3.4.0
- Cloud: 2.7.2
Improvements
- Environment state storage model has been reworked to prepare for upcoming features
- Web: An environment's undeployed components now show the type of change (added/modified/removed), and a clearer reason why the component is undeployed
July 12, 2025
- Web: 1.1.1
- CLI: 3.3.1
- Cloud: 2.7.1
Fixes
Fixes an issue where outbound flows using history diff might miss components to be deployed if include specs had changed.
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 --maxDeployAttempts 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
June 21, 2025
- Web: 1.0.1
- CLI: 3.2.4
- Cloud: 2.6.17
Improvements
- Updates links throughout the product to align with updated website and docs URL scheme
- CLI: Improves the output of the
orgflow --helpcommand
June 19, 2025
- Web: 1.0.0
- Cloud: 2.6.16
June 7, 2025
- CLI: 3.2.2
Fixes
- Fixes an issue where Salesforce authentication could sometimes fail with
INSUFFICIENT_ACCESS: Inactive Organizationfor a recently refreshed sandbox
May 30, 2025
- CLI: 3.2.1