Hi Matt, Thank you for your help. I'lll try to give you more context about the issue. Yes, all the nodes of the cluster run the same version: 1.15.3 and the same libs. Unfortunately, shutting down the entire cluster is not an option because it is a production environment and it receives live streaming data we cannot afford to lose. We operate the environment this way: we create the process groups, flows and configurations on a staging cluster (3 nodes, same NiFi version 1.15.3). We commit the changes to the registry Then we pull them to the production cluster (11 nodes) from the registry. This is why I'm sure that the configurations stored in the registry are valid and working: the same process group on the staging cluster has no issues. Are you saying that if you access the NiFi UI from a different node in your 11 node cluster, this process groups renders differently? No, the process group renders the same on all nodes, but every attempt to do anything on it results in the same error message: We cannot edit it, delete, change version, detach from version control, not even move it. It always returns the same error, albeit no modification is present locally. In fact, the version control menu seems to "believe" that there are local changes to the PG: But then, if I select "Show local changes", nothing is shown, as expected: Same if I select "Revert local changes": My assumption is that the process group definition in the local flow file is corrupted or not in sync with the version control of the registry. So I think that the best solution is to just force-delete the PG and the re-create it. Is there a way to do this? Thank you S
... View more
