When deploying a new version of a Flow, Salesforce does not always automatically deploy updated versions of the Flow’s existing translations unless those translations are included in the deployment package.
To help avoid missing translations after a flow deployment, Gearset provides and optional Problem Analyzer fix called Flow no difference translations. When enabled, Gearset will automatically include a copy of the flow translations from target in the deployment package, ensuring that existing translations are maintained after the deployment.
Why this happens
Flow translations in Salesforce are stored separately from the Flow metadata itself.
If a Flow is deployed without its translations, the target org may end up with the new Flow version but without the expected translated content, which can require a
follow up deployment.
How this works
For this feature to work as expected, the following must be true:
Flow on target is either active or obsolete (it will not fire on draft flows)
Translation for the flow exists on target
The translation in question is not already included in the deployment
This will show up as an unchanged translation being deployed in the deployment summary.
Disable the fix if you don’t want Flow translations included
If you prefer to deploy Flows without automatically including Flow translations, you can disable the fix in your Problem Analyzer template: You can check this article for more information about customizing the template.
Go to Account
Select Problem analyzer templates
Open your template
Go to Add change to deployment
Disable Flow no difference translations
Once disabled, Flow translations will only be deployed when you explicitly include them in the deployment.
CI job filter considerations
If you are using a CI job, your metadata filter must allow both metadata types Flow + Translations for them to be included in deployments.
If your filter excludes Translations, Gearset will not be able to deploy them even if the Problem Analyzer fix is enabled.
Please check this article to see how to apply the customized problem analyser template in a CI job.