Hello @MattWho, Thanks for your quick answer. What's make me feel it's more on NiFi side it's that we have the error on at least one maybe two environments but not the others two. Now I have succeed to revert to last version of the bucket for 2 nodes on 3 but if I up again the third one, I have temporary a question mark on the bucket itself then the asterisk without any way to display local change. When I create a process just to generate local change then I have difference between the two first node and the third one. We plan to upgrade the Registry after the upgrade of NiFi but as you say it's pretty mandatory. Do you think I can upgrade from Registry 0.7.0 to last one version then after upgrade NiFi to last 1.x release ? For the log I'll check and come back to you but as I saw for the moment, nothing seem very explicit. That's why I thought about a file/folder that store local changes. Finally, for your note, I know about the flow.xml.gz that not used anymore but as we go from 1.13.2 we still have it. Even if I copy flow.xml.gz, flow.json.gz or both of them from a working node, it won't start and error on flow desync. Thanks.
... View more
