Hi. I haven't found any documentation for these internals about the InvokeHTTP processor in NiFi. My requirement is to throttle requests to and endpoint (which we also control) that will accept, let's say, 5 simultaneous connections in an address and port, but I need to wait for each of their responses before letting another flowfile to be sent, so:   Does this translate to simply using 1 InvokeHTTP processor configured to 5 "Concurrent Tasks" and that's it? Will the processor wait for the remote endpoint's request before sending the next one? How does the "Run Schedule" works together with the previous settings? (if I had, e.g.: 1 sec) I've been proposed with splitting the incoming queue and put 5 InvokeHTTP processors in parallel, each one attending 1/5 of the incoming flowfiles (I'd do the pre-partitioning before with some RouteOnAttribute trick), but I think it's exactly the same outcome as the 1. above. Is it? This all boils down to not knowing exactly how this processor work under the hood. Any insight would be much appreciated, thanks in advance! ... View more