We Encountered this Issue whenever we try to Deploy/Validate any of Changes to Higher Environments like SAT or UAT through Jenkins. Basically, It started creating a new version of flows every time whenever we deploy/validate our branch components.
We have tried to Add the Flow Definition with Active FlowVersion, But That is not Worked.
Please Let us Know, how to tackle with this Issue.
8 respuestas
Hey, I know this is a year old but this worked for us:
- Initially, deploy or make your flow in org
- Create your package with the active version of this flow
- In the flow-meta.xml metadata file that you keep in source control, delete BOTH of the following tags:
- <status></status>
- <apiVersion></apiVersion>
- Commit the cleaned out flow-meta.xml, and that should prevent further incrementation.
When you want new changes committed, just add those tags back in by retrieving your updated flow.
