Sign In
Create your first automation in just a few minutes.Try Studio Web →
Check Cron Collision
by Internal Labs
0
Activity
<100
Summary
Summary
This activity checks if 2 cron expressions collide with each other in a certain year.
Overview
Overview
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.
Features
Features
Prevent schedule jobs colliding/conflicting with each other.
Additional Information
Additional Information
Dependencies
This package uses .NET default system packages only.
Code Language
Visual Basic
Runtime
Windows Legacy (.Net Framework 4.6.1)
Technical
Version
1.0.0Updated
April 20, 2022Works with
Studio: 18.4 - 22.10
Certification
Silver Certified
Support
UiPath Community Support
Similar Listings
