@wasabipeas @Adhitya  In the thrown exception it reports which node has the mismatched revision. Is that node the currently elected cluster coordinator? Have you tried on just that reported node: 1. Stopping NiFi 2. Remove or rename both the flow.xml.gz and flow.json gz files (only deleting one will not work) 3. Restart that NiFi node.  It will inherit the flow from the cluster coordinator when it joins. If this node was the elected cluster coordinator, when you shut it down another node will assume the cluster coordinator role. ---- Another option is to disconnect the node reporting the mismatch in revision.  Then from the same cluster UI used to disconnect that node, select to drop/delete it from cluster.  Your cluster will now report one less node.  See if you can then move the process group or if it reports another node with mismatched revision? NOTE: Deleting/Dropping a node from cluster using the Cluster UI does nothing to that node.  If you restart that node that was deleted/dropped it will rejoin the cluster again.   Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

@Adhitya, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future. ... View more

@Adhitya, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future.  ... View more

@Adhitya This is a rather old post.   Can your provide details on your specific setup (processors and configurations including scheduling) used,  info around your data and what you expect versus what you are seeing? Is your NiFi a cluster setup or standalone? How is source data ingested into your NiFi for this dataflow? Typically issues like this are related to dataflow design, but there is not enough info here to reproduce or make suggestions yet. Thanks, Matt ... View more

Thank you for your response cotopaul. In MQTT 5 there is a feature for Request-Response, in that feature there is a field setting to determine the response topic (different from the actual topic). The response topic field represents the topics on which the responses from the receivers of the message are expected. I was wondering if maybe NiFi could get the response topic field value from the MQTT as an attribute ... View more