@Vapper  Maybe I am not 100% clear on your question here.. When you say new "flow file" I assume you are talking about the flow.xml.gz file? In NiFi, a "FlowFile" is what you see being queued on connections between processor components and consists of FlowFile content and FlowFile Metadata/Attributes. In a NiFi cluster, all nodes must be running the exact same flow.xml.gz.  If the dataflows loaded from the flow.xml.gz do not match the node will not be allowed to join the cluster.  In the latest releases of NiFi, Nodes joining a cluster will inherit the cluster dataflow if the local dataflow does not match. Once a cluster is established, a cluster dataflow is elected. That becomes the clusters dataflow. Joining a node to that established cluster will require that joining nodes is using same flow.xm.gz as existing cluster and if not inherit the cluster elected dataflow over the existing flow on the joining node. NiFi will not assume that a joining nodes flow.xml.gz is "newer" or "desired" over the elected cluster dataflow and replace the elected cluster dataflow with that new dataflow. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt ... View more

@Vapper  In a NiFi cluster each node executes its own copy of the flow.xml.gz, has its own set of repositories, and executes against only the FlowFiles on that specific node.    So you need to consider this in your dataflow designs. Perhaps the dataflow that executes the groovy Script on all nodes could be designed to write all the produced files to a single destination server.  Then in your http_request-> fetchfile-> http_response dataflow, instead of "fetchFile" use fetchSFTP to retrieve all those files and mergeContent to merge in to one file before the http_response. If you found this response assisted with your query, please take a moment to login and click on "Accept as Solution" below this post. Thank you, Matt   ... View more