October 20, 2026

• CLI: 3.7.28
• Cloud: 2.13.26

Improvements

• Improves org data import resilience by waiting and retrying batch creation in the event that the target org has exhausted available Bulk API batches.
• Improves logging when items of a metadata type cannot be listed in an org, so that the specific type that was rejected can be identified.

Fixes

• Fixes an issue where nested components inside an added composite component could sometimes be included in the deployment archive but omitted from its package manifest.
• Fixes an issue where nested components that cannot be deployed (such as those belonging to a managed package) were incorrectly included in the deployment archive when their parent composite component was added and could itself be deployed.
• Fixes an issue where a permanent error from the Salesforce Metadata API, such as a metadata type that the org does not allow to be listed, was treated as a temporary one and retried for many hours before the operation eventually failed.
• Fixes an issue where a single metadata type that the org does not allow to be listed would cause the other types queried alongside it to be silently omitted from the results, so that components that do exist in the org were missing from retrieved metadata.
• Fixes an issue where listing the folders of a folderized metadata type, such as Report or Dashboard, would fail with an unexpected error if the org contained no folders of that type.
• Fixes an issue where retry and timeout settings intended for one type of Salesforce API call could be applied to other types of calls as well, causing those calls to be retried for much longer than configured.
• Fixes an issue where the configured retry and timeout budgets for calls to Salesforce could be compounded, causing a failing call to be retried many more times, and for far longer, than configured.
• Fixes an issue where OrgFlow could sometimes select a Salesforce API version that is newer than the most recent version it has support for.
• Fixes an issue where a flow in with the "force" option enabled neglected to delete metadata that had been recently excluded from .orgflowinclude.
• Fixes an issue where a flow out could fail with an unexpected error when a component that failed to deploy had a name containing characters that OrgFlow did not expect, such as the moderation rules, keyword lists and member criteria of an Experience Cloud site whose name contains a hyphen.
• Fixes an issue where documents belonging to a managed package (such as FSL__Field_Service_Documents/FSL__Logo.png) were not recognized as namespaced, and were therefore matched by include specs for non-namespaced metadata and treated as deployable.
• Fixes an issue where the namespace prefix of an object was removed from the names of its layouts when matching them against include specs. Include specs targeting layouts of objects from managed packages must now include the namespace prefix of the object name, for example unpackaged/~/Layout/FSL__Polygon__c-*.