Hi umair, @umair_ahmed , @Wynner , @Matt Clarke The retry mechanism of the unmatched records from the invoke HTTP which was very helpful. Could you please more elaborate information on the advanced settings of the Update attribute. And the Route attribute and Execute stream command. 1) 5 times it needs to retry but only four times it has been mentioned in advanced property of the update attribute. And the expression on the advanced setting of the update attribute needs to be : ${retry.counter:replaceNull('0'):equals('1')} whether it needs to be in the incremented fashion like  sleeponeminute -> ${retry.counter:replaceNull('0'):equals('1')} sleepthirtyminute ->  ${retry.counter:replaceNull('0'):equals('2')} sleeponehour ->  ${retry.counter:replaceNull('0'):equals('3')} sleeptwohours ->  ${retry.counter:replaceNull('0'):equals('4')} sleepmaxcount -> ${retry.counter:replaceNull('0'):equals('5')} (i.e., the sleeptime for the sleepmaxcount rule set to 180m)  2) For the RouteOnAttribute, I have set the 5 conditions as per your screenshot. I can see the flowfile between the connector updateattribute and RouteOnAttribute then i couldn't see the flowfile in the next connector.  Could you please elaborate more on the property setting of the other two processors Routeon Attribute and Execute StreamCommand(CommandPrompt property: It states take the environmental value ). Working Directory and Output destination attribute could you please explain these properties as well.   Thanks in Advance, Karthick    ... View more