Actually, I think that would be fine. Mark Payne can chime in and correct me if I'm wrong, but as far as I know, when changing a flow to a new version, not every series of changes is applied, but rather, the diff between the current version and the new version is computed and applied. 

So in this case, if you rename the port that is causing the IllegalStateException to give it a unique name, and then change from the previous version to your newest version (skipoping the offending change that triggers the bug case), it _should_ avoid the issue.

Hope this helps get you past the current blocker!

On January 10, 2019 at 16:50:41, Russ Weiher ([EMAIL PROTECTED]) wrote: