Incorrect Retrieval of flow/flowDefinition
u0420273 opened this issue · comments
The implementation lists a "suffixless" version of a flow in the manifest, which wouldn't match a respective instance of the flow in an Org, or retrieve its metadata file. To fix this, a matching flowDefinition should be retrieved first, and parsed to determine a correct version number, which should then be appended to a stem of the "suffixless" file name.
I ran into this issue several times. I am working on submitting a fix for this.