We are having an issue deploying a flow using a yaml file.
The flow was deployed properly using the i3 file format, but when we try to include the exported yaml in our pipeline we get the following error:
the property 'transferToUser' cannot be assigned a value. Please be sure that this property can be assigned a value in this context. For example, some properties are not available in certain flow types but are in others or are conditionally writable based on the value of another property.
We don't understand why this is happening as the yaml we're trying to use is a direct export from the environment with no changes done to it. The only cause we could think of would be a "permission" issue, but we already tried assigning all the permissions to our OAuth we could think of.
There appears to be a bug where these properties appear to be added to the yaml export when they should not be. This should be fixed in the next Architect UI deploy.