Hi @brajeshreddy , I dont think you can achieve this using the ControlRate processor. Instead I recommend the solution mentioned here: https://stackoverflow.com/questions/69893107/nifi-activate-a-flow-file-after-a-previous-flow-file-goes-through-the-downstre   If you have a cluster then make sure that the top processor is executing on the Primary node.   hope that helps. Thanks   ... View more

Hi @Diga , Here are some videos to help you get started with the InvokeHttp Processor: https://www.youtube.com/watch?v=aNrdWYy4i34 https://www.youtube.com/watch?v=SZhX_gce63E https://www.youtube.com/watch?v=Jk7H8w3evN0   As far as logging in and authentication, it depends what kind of authentication the Rest API has. If it has simple authentication (username & password) you can enter those in the Basic Authentication Username & Basic Authentication Password properties. If you need to get Access Token (OAuth2) then you either obtain this through another InvokeHttp processor and pass it to the actual rest api invokehttp as "Authorization" header property (dynamically added to the processor), or second option is to take advantage of the "OAuth2 Access Token provider" in the InvokeHttp processor by setting up "StandardOauth2AccessTokenProvider" service and provide the credentials  and the access token url there.   Hope that helps. Thanks   ... View more

Hi @CommanderLaus , If you do anything manually with the processor you are trying to change its Running State through the API, then yes the revision will be updated. In my case what I do is basically the first API InvokeHttp is to get the latest revision using the following GET API:   https://localhost:8443/nifi-api/processors/${pipeline.start.processor.id}   This will give the following response where you can parse the latest "version" value using something like EvaluateJsonPath processor and store the value in an attribute:   { "revision": { "clientId": "value", "version": 0, "lastModifier": "value" }, "id": "value", "uri": "value", "position": {…}, "permissions": {…}, "bulletins": [{…}], "disconnectedNodeAcknowledged": true, "component": {…}, "inputRequirement": "value", "status": {…}, "operatePermissions": {…} }   Then use extracted version attribute to build the next API post Body , for example in my case I use ReplaceText processor to generate the post body :   { "revision": { "clientId": "${pipeline.start.processor.id}", "version": ${processorVersion} }, "state": "...", "disconnectedNodeAcknowledged": true }   Hope that helps.       ... View more

@MattWho, @steven-matison , @cotopaul ...Can you guys help with this? ... View more