a6e5b969-be6e-4756-ae53-47d3cb899ca4.png

Customer Success Manager

e0f14ab1-4e2f-4547-96ad-2614bc24048b.nupkg

Often times we see customers have a problem in scheduling unattended jobs. Especially when 2 complex advanced cron expressions are involved.

  

This activity checks 2 cron expressions in a certain year at a time. You can either query the DB or using Orchestrator API to get all the cron expressions each time triggers are scheduled. Then loop this activity to check if each pair of cron jobs has conflicts in a certain year.

  

Please note that the collision must happen within the same year, month, day, hour, minute, and second. If you want some buffering, the current workaround would be to change the cron expression by yourself. 

  

E.g. change the first 2 symbols in a cron expression to 0 before feeding into this activity. This means the scheduled job takes place every 0 minutes 0 seconds in that hour.

This activity checks if 2 cron expressions collide with each other in a certain year.

Check Cron Collision