Understanding and creating Cron expressions

Help Orchestrator
, , , , , ,
1

I have a cron expression “0 0 0-6 ? * SUN,MON,TUE,WED,THU,FRI,SAT *” that i want to use in orchestrator, does this expression mane that between the hours of 12am and 6am items with in the queue would be picked up? then once outside this hours the items would stop being processed in the queue until the next day between the hrs of 12 am and 6 am?

scenario - there’s 80 items in the queue between 12am and 6 am will the bot work 1 case and hour or will it work multple case with in that hour once outside this time the cases will stop?

2

@duaine.b

Yes the bot will get triggered daily between 12AM to 6 AM every hour…

And when it triggwrs it would try to complete all the items that are present in the queue in new state…

And no it would not stop after 6 if there are more queue items…ie., say bot starts at 12,1,2,3,4,5,6 …every hour…now …say when the bot started at any of these timelines and say there are 100 queue items …then bot will try to complete all 100 and only then it stops… but say if the bot has completed 100 items by 6:30 AM and a new queue item is added after the bot stopped…then the item is picked up on the following day at 12AM again when the bot starts for thw first time the next day…

The trigger is only for start of the bot not to end the execution of the bot…

Please check this for cron expression help

image
image828×704 97 KB

Hope this helps

Cheers

1 Like
3

@Anil_G thanks for the comment "For stopping you have another option while setting trigger…you can give the stop after time…after which the bot will stop processing the items even if there are more queue items left

Hope this helps.

Cheers" from the other post so if i use the same cron expression and then enable end job execution set the hh to 6 does that mean that the process will run as many cases as it can then stop after 6 then resume again the next day at 12am?

4

@duaine.b

Yes that is true… but just think. If you set the trigger till 6 then bot will start at 6 and as your stop after is also 6 it will immediately terminate… so either change your cron to 12 to 5 and set stop after at 6 or have trigger from 12 to 6 and change stop after accordingly

Cheers

5

That makes sense, will change the logic to 12-5 then have the stop at 6 hh. If let’s say there’s 100 items in the queue and the bot is on the 40th case will it complete the 40th case then stop and resume the 41st case the following day or would it stop half way through the 40th case then resume the 40th case the following day?

6

@duaine.b

While specifying the time you can as well specify whether the bot needs to stop immediately or it should stop after completing the current running transaction…do not seect kill…select stop so that it stops after completing the current transaction

So if you set kill it will leave 41st item in inprogress and end the job…

If set to stop then 41st item is completed amd then stopped

Cheers

7

Ahh make sense, in the instances a case fails assume if the retry is on the case will still retry

8

@duaine.b

If queue retry is enabled then new item
Would be added but qont be picked until next day if the time Is crossed

Cheers

9

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.