@Prabir Guha I did a quick test and your regex worked just fine. What does your original flow file name look like? ... View more

@umair ahmed Okay, that is the expected behavior. Try the exact command in the ExecuteStreamCommand processor and see if it works? Just use the flow file as a trigger for the processor. ... View more

@umair ahmed Try changing "notanerror" to something else and see if you still get the error. I just put that as an example. Open a cmd window on your system and see if you can run the command outside of NiFi. Try something like, waitfor /T 10 test ... View more

@umair ahmed I see the issue. While the values for sleeptime are in seconds, do not put the unit in the value. So, instead of 1800s, change that to 1800 and so on for the other values. ... View more

@umair ahmed What do you have in the property Command Arguments in the ExecuteStreamCommand processor? Please take a snapshot the Properties tab for the ExecuteStreamCommand processor. When I said you need to have the value in seconds for the sleeptime attribute, I meant inside the configuration of the advanced UI in the UpdateAttribute processor. In the template I uploaded, I was using minutes. ... View more

@umair ahmed You are correct, it is a Windows problem. The timeout command does not work with input redirection. So, use the waitfor command and it will work, here is a snapshot of the reconfigured ExecuteScriptCommand processor: Even though it works, the waitfor command throws an error because the notanerror event never occurs before the time out period. Also, the sleeptime values have to be in seconds, not minutes or hours. ... View more

@umair ahmed I am not following you. What do you mean by "firing every 30 sec for 5 counts"? I just used the delay times as en example. How long do you want it to wait each time through? In my template, iI did the first time 60 seconds, second time 30 minutes, third time 1 hour, fourth time two hours. ... View more

@umair ahmed Correct, just replace /usr/bin/sleep with timeout. What version of Windows are you using? ... View more

@umair ahmed That is a command in Unix, to wait the amount of time specified, 30 seconds, one minute whatever is specified. The Windows equivalent is timeout I believe, so just replace the command. ... View more

@HAR MAT You can use the CRON driven option in the Scheduling strategy to have the flow run once. Or use the rest api to run the processor once. Here is an example using the cron option, the below processor will run once on May 8th, 2017 at 10AM ... View more