Automating Workflows using HCL Universal Orchestrator: Implement EVERY on Job

Introduction
Embracing Automation for Repetitive Tasks: The Key to Efficiency

​In today’s fast-paced digital world, efficiency is no longer a luxury—it’s a necessity. One of the most effective ways to achieve efficiency is through automation. Automation has become the backbone of modern workflows, particularly for repetitive tasks that consume time and resources. It ensures accuracy, consistency, and optimal resource allocation, enabling businesses to focus on innovation. In HCL Universal Orchestrator (UnO), attributes like ‘repeatInterval’ and ‘skipLateAction’ enhance automation by providing fine control over task scheduling and handling missed executions. Let’s explore these features, focusing on their behaviour and practical applications.
 
Why Do We Need Automation for Repetitive Tasks
Repetitive tasks are often necessary but time-intensive and prone to errors. Some examples of repetitive tasks include data entry, report generation, and system monitoring. Automation offers several benefits for such tasks:
Timesaving: automation removes the need for manual intervention, freeing up resources for strategic priorities.
Error reduction: automated tasks run consistently, minimizing human-induced errors.
Scalability: automation can handle large-scale operations without additional effort.
Reliability: scheduled tasks run at precise intervals, ensuring workflows remain uninterrupted.
 
Leveraging the repeatInterval (EVERY) Attribute
The repeatInterval (EVERY) attribute defines how frequently a task should repeat within a given timeframe. This removes manual rescheduling, optimizing task efficiency and increasing productivity.
In UnO, the repeatInterval attribute is simultaneously being used in multiple places, but here we talk specifically about how this feature can be incorporated in tasks.
 
Note: The maximum value for the repeatInterval attribute is 99 hours 59 minutes, in the hh:mm format.
Key Requirement: LatestStartTime
For the repeatInterval attribute to work effectively, the LatestStartTime parameter is mandatory. This parameter defines the endpoint for task execution, indicating the time until which the repeated tasks will run.
For example:   
Scenario: A data synchronization job must run hourly and stop after 24 hours.
Configuration:
repeatInterval = 1 hour
LatestStartTime = CurrentTime + 24 hours
This configuration ensures that the data synchronization job runs consistently within the specified timeframe and stopping at the specified time without human oversight.

​Managing Missed or Delayed Tasks: The skipLateAction Attribute
In real-world scenarios, tasks may be delayed or missed due to system downtimes, resource unavailability, or high workloads. The skipLateAction attribute offers flexibility in handling such situations, with three distinct values:
 
Scenario:
Planned Run Time: 12:15 PM
Current Time: 12:25 PM
Next Planned Run Time: 12:40 PM
1. SKIPLATE = NONE
The missed task at 12:15 PM will be run immediately.
All the other tasks will continue as per the planned schedule in sequential order.
Real-time example:
 
Use case: a log aggregation service that must process every log entry.
Behaviour:
At 12:25 PM, the missed run (12:15 PM) will be submitted first, ensuring no data loss. The system then continues processing tasks in sequence, starting with the 12:40 PM run.
2. SKIPLATE = OVERLAP
In this case the system first checks whether it’s time to run the next scheduled task (12:40 PM).
If yes: The late run (12:15 PM) is suppressed. However, an entry for this task is made in the database, indicating that a planned task run has been missed or suppressed.
If no: The late run (12:15 PM) is run immediately.
Real-time example:
Use case: A promotional email scheduler that avoids sending multiple emails simultaneously to users.
Behaviour:
At 12:25 PM, the system suppresses the missed 12:15 PM email if it’s close to the next scheduled email. If there’s enough time, the missed email will be sent immediately.
3. SKIPLATE = IMMEDIATE
Here the system uses a predefined interval (UNO_EVERY_IMMEDIATE_INTERVAL_IN_MINUTES, default: 2 minutes, which is set in the configuration file) to decide what to do.
If (next planned time - current time) > interval: the late task is submitted.
Otherwise: the late task is suppressed.
Where the next planned time is the next occurrence of the task run as per the schedule set by the repeatInterval option, and Current Time is the time when the server or agent is back online.
Real-time example:
Use case: a financial transaction system that processes overdue transactions quickly but avoids processing them too close to the next cycle.
Behaviour:
At 12:25 PM, the system evaluates the gap between the current time and the next planned time (12:40 PM). If the gap exceeds the 2-minute threshold, the missed run is processed immediately. Otherwise, it is suppressed to prevent redundancy.
Choosing the Right Configuration
The choice of which skipLateAction to use depends on the task’s criticality and system constraints:
NONE: ideal for scenarios where every missed task must be run to maintain data integrity or ensure comprehensive reporting.
OVERLAP: best suited for tasks where duplicate processing is undesirable, such as user-facing notifications.
IMMEDIATE: perfect for time-sensitive operations where catching up on missed tasks depends on the proximity to the next planned run.
Conclusion
Automation is no longer a convenience—it’s a strategic necessity. By leveraging attributes like repeatInterval for scheduling and skipLateAction for handling missed tasks, HCL Universal Orchestrator offers robust and efficient solutions. Choosing the right configurations for these attributes guarantees tasks are run with precision, aligning with organizational priorities and system capabilities.
Automation empowers teams to focus on what truly matters: innovation, creativity, and growth. Adopt automation today and transform routine tasks into seamless processes that drive efficiency and excellence.

Author

---

Akanksha Mani – Senior Software Engineer at HCL Software
Akanksha is a part of UnO Backend QA team working in Bangalore. She serves as an Automation tester in the Workload Automation project. She has prior experience in IBM for more than 4 years before joining HCL Software. She has completed her graduation from West Bengal University, Kolkata. Having worked on different forms of testing, currently API testing is what she works on, having knowledge in some of the in-demand technologies like Java, Rest API, MySQL, Git, MongoDB with testing platforms such as Selenium, Postman, RestAssured as well. She loves playing Badminton, Table tennis and Chess.