Jobs
The Jobs tab in the AutomatR Orchestrator application provides a centralized location to manage and monitor the execution of automation processes or jobs. It offers valuable insights into the status and history of jobs, enabling users to track progress, view details, and take appropriate actions as needed. You can start, stop, and schedule automation tasks. Monitor the progress of each job and review execution logs for troubleshooting and performance analysis. Below are the key sections found in the Jobs tab:
| Field | Description | ||||||
|---|---|---|---|---|---|---|---|
| Job | The Job column displays the names or identifiers of the different automation jobs that have been executed or scheduled. Each job represents the execution of a specific automation process or flow. | ||||||
| Flow | The Flow section shows the names or identifiers of the automation flows associated with each job. It indicates which automation process the job is executing. | ||||||
| Run Type | The Run Type column denotes how the job was triggered or initiated. It differentiates between different ways jobs are started, such as manual (user-triggered) or scheduled. | ||||||
| Scheduled Type | The Scheduled Type column indicates whether the job was scheduled to run at specific times or intervals. It helps users identify jobs that were automated based on predefined schedules. | ||||||
| Created On | The Created On column displays the date and time when the job was created or scheduled. It provides users with a reference point for when the job was initiated. | ||||||
| Last Run | The Last Run column shows the date and time of the most recent execution of the job. It gives users an overview of the job's recent activity and helps track the job's frequency. | ||||||
| Status | The Status section provides real-time information about the current state of each job. The job statuses include:
|
The Jobs tab in the AutomatR Orchestrator application serves as a vital tool for managing and monitoring the execution of automation processes. It empowers users to oversee ongoing automation activities, access job-specific details, and perform necessary actions to ensure smooth and efficient automation operations. The ability to search for jobs by name adds to the user's convenience and enhances the overall user experience in managing their automation workflows.
Add Job
Here's a brief step-by-step procedure to add a Job in an AutomatR Orchestrator application:
Log in to the AutomatR Orchestrator application with appropriate credentials.
Once logged in, navigate to the Jobs section or tab where you can manage and create new jobs.
Look for an Add button to initiate the process of creating a new job. Click on the button to proceed with adding a new job.
A form appears where you need to enter the details for the new job.
From the drop-down menu, select the desired automation Flow and its corresponding Version. This identifies the specific automation process that the job will execute.
Enter the following job details in the provided fields:
- Job Name: Provide a descriptive name for the job to easily identify its purpose or function.
- Email: Input the email address where job-related notifications and alerts will be sent.
- Configuration: Choose the appropriate configuration from the available options that define how the job will run.
From the drop-down menu, select a log levels for the job, such as Verbose, Debug, Information, or Error. This determines the level of detail in the job logs. For more details refer Log Level section.
Specify the screen resolution for the job with options for both width and height. This setting ensures the proper display of the automation process on the designated target machines. The screen resolution setting helps to optimize the automation flow's user interface, interactions with elements on the screen, and overall visual display. You can enter the preferred values or the common standard resolution values mentioned below:
Resolution Description 1920x1080 This is a Full HD resolution with a width of 1920 pixels and a height of 1080 pixels. It is widely used and suitable for most modern desktop and laptop computers. 1366x768 This is a common resolution for laptop displays and certain monitors. It has a width of 1366 pixels and a height of 768 pixels. 1280x1024 This is a standard resolution for certain desktop monitors. It has a width of 1280 pixels and a height of 1024 pixels. 1600x900 This is a widescreen resolution with a width of 1600 pixels and a height of 900 pixels. It is commonly used in laptops and monitors. By configuring the screen resolution appropriately, automation developers can ensure that their automation processes are visually optimized and effectively interact with elements on the screen, resulting in seamless and efficient automation execution.
Utilize the Select Bot(s) option to choose the bot(s) that will execute the job. Additionally, select the desired configuration for the selected bots if applicable.
From the available Run Type options (Run Now, Run Later, and Recurring), choose the appropriate one for the job.
Here's more detailed explanation of the three Run Types:
Run Type Description Run Now The Run Now option in the Run Type allows users to execute a job immediately without delay. It is designed for on-demand execution of automation processes when users need the job to start right away, regardless of any predefined schedule. When users select Run Now, the job is triggered immediately, and the Orchestrator initiates the execution as soon as possible.
Use Cases:
- Ad-hoc Tasks: Running a one-time job immediately to address a specific need or perform a critical task outside the regular schedule.
- Testing: Executing the automation flow in a production-like environment without waiting for a scheduled run to verify its functionality.
Advantage
- Offers flexibility and immediate execution for urgent or time-sensitive tasks, allowing users to perform ad-hoc jobs on-demand.
Run Later The Run Later option enables users to schedule a job for execution at a specific future date and time. When choosing this option, users can set the desired date and time for the job to start, and the Orchestrator will automatically initiate the job at the scheduled time.
Use Cases:
- Preparing for Upcoming Tasks: Scheduling a job to run at a later time when a specific task needs to be performed in the future.
- Off-Peak Execution: Scheduling the automation job to run during non-peak hours to avoid resource contention or ensure better performance.
Advantage
- Provides the convenience of scheduling tasks to be executed at a specific time, ensuring that critical activities are performed as planned.
Recurring The Recurring option allows users to set up a job for repeated and automatic execution at specific intervals. Users can define the frequency of repetition (e.g., daily, weekly, monthly) and specify the interval between each run. The Orchestrator will automatically trigger the job at the defined intervals.
Use Cases:
- Daily/Weekly/Monthly Tasks: Scheduling automation processes that need to run on a regular basis, such as generating daily reports or performing weekly backups.
- Periodic Checks: Automating tasks that need to be performed at specific intervals, like system maintenance or database cleanup.
Advantage
- Saves time and effort by automating jobs to run at regular intervals, be it daily, weekly, or monthly, to handle repetitive tasks and periodic checks efficiently.
These three different Run Types allows users to efficiently manage the timing and execution of automation jobs, providing the flexibility to adapt to various scheduling needs and optimize automation processes.
Start Grace Time is a configuration setting in automation that introduces a delay before starting the execution of a scheduled job. It allows a job to wait for a specified duration after its scheduled start time before actually beginning its execution. The purpose of the Start Grace Time is to provide some flexibility in job execution, especially in scenarios where multiple jobs are scheduled to run at the same time, or when system resources are busy with other processes.
Considerations - Duration Selection: The duration of the Start Grace Time should be chosen thoughtfully. It should be long enough to accommodate potential resource contention or delays but not excessively long to cause unnecessary delays in execution.
- Job Priority: While Start Grace Time provides flexibility, it is essential to consider the priority and criticality of the job. Some jobs may need to start immediately, while others can tolerate a short delay.
How Start Grace Time Works - Scheduled Start Time: When a job is scheduled to run at a specific date and time, the Orchestrator initially waits until the scheduled start time is reached.
- Grace Time Delay: After the scheduled start time is reached, the Orchestrator waits for the duration specified as the Start Grace Time before initiating the job's execution.
- Flexibility in Execution: The grace time gives the Orchestrator some flexibility to wait and allocate resources for the job. If the system is busy with other high-priority tasks or if multiple jobs are scheduled to start at the same time, the grace time helps prevent resource contention and potential bottlenecks.
- Actual Job Execution: Once the Start Grace Time expires, the Orchestrator starts the execution of the job, ensuring a smoother and more controlled process start.
Advantages of Start Grace Time - Resource Management: Start Grace Time helps prevent resource overload by allowing jobs to wait for a brief period before starting. This improves overall system efficiency and reduces the risk of resource contention.
- Avoiding Race Conditions: When multiple jobs are scheduled to run simultaneously, the grace time helps avoid race conditions and ensures that each job gets sufficient resources for successful execution.
- Resilience to Delays: In case of any delays in resource availability or system readiness, the grace time allows the job to wait and avoid execution errors due to resource unavailability.
In summary, the Start Grace Time in automation allows for a controlled and efficient job execution by introducing a brief delay before starting the execution of a scheduled job. It enhances resource management, improves system efficiency, and helps prevent potential issues related to resource contention.
Review all the entered details to ensure accuracy. After verifying, click the Add button to create the new job.
After clicking the Add button, a confirmation message may appear, indicating that the job has been successfully added to the Orchestrator.
You have now successfully added a new job in the AutomatR Orchestrator application, specifying all the necessary options for its execution. Depending on the configuration and permissions, you may have additional options available for further customization and management of the job.
Update Job
The Actions column in the Jobs table provides options to interact with individual job and allows you to modify the job's details or parameters, such as scheduling settings or input data.
In the Actions column associated with the job, click on the Edit option.
Upon clicking Edit, a form will appear displaying the selected flow information.
Enter the necessary details for updating the job:
Name: Update the name of the flow.
Package Name: Update the package name of the flow.
Automation Type: From the drop-down menu, select the appropriate automation type for the flow. The available options are Attended and Unattended. For more details refer Automation Type section.
Double-check the information you entered for accuracy, ensuring that the flow name, package name and automation type are correct.
Once you are satisfied with the flow details, click on the Update button to finalize the updation of the flow.
Upon successful addition, you will receive a confirmation message or notification stating that the job is updated. Navigate back to the Jobs tab and review the table to ensure that the updated job appears with the name, flow and run type you provided.
Delete Job
The Actions column in the Jobs tab provides options to interact with individual job, the Delete option from the Actions column of Jobs table allows you to remove the job from the AutomatR Orchestrator. Use this action for permanently removing the job from Orchestrator or when it is no longer required in your automation infrastructure.
Clone Job
AutomatR Orchestrator's Jobs Tab allows users to clone a job, making it easy to replicate and rerun automation processes with minimal effort. Here's a step-by-step guide on how to clone a job:
Log in to AutomatR Orchestrator and navigate to the Jobs tab, which displays a list of jobs and their related details.
In the Jobs Tab, locate the specific job you want to clone from the Jobs table.
Find the Actions column associated with the job and click on the Clone option.
Clicking on the Clone option opens a form with the job details pre-populated.
Review the pre-populated job details to ensure accuracy.
If necessary, update any available fields in the form. For example, you may want to change the job name, job configuration, or other relevant information.
After confirming or making any required updates to the job details, click on the Clone button to initiate the cloning process.
The system will create a new job with the same configuration and settings as the original job.
Upon successful cloning, you will receive a confirmation message indicating that the job has been cloned.
The cloned job will now be available in the list of jobs, ready for execution.
Cloning a job in the AutomatR Orchestrator Jobs Tab is a convenient feature that allows users to replicate automation processes quickly and efficiently. By following these steps, users can create copies of existing jobs, making it easier to rerun tasks with the same configuration and settings, ultimately streamlining the automation workflow.