To add a new Job, click on the relevant Project, and then click New Job in the top right corner.
When creating a job, there are several fields and details that can be provided to customise the behaviour of your job. These include:
This is a unique label to identify your job, it can be changed at anytime without affecting the underlying tasks and scheduling.
The Logging Level refers to how detailed the success or failure logs will be after running a Job.
|Level||Details||Types of Logs|
|Standard||This setting will produce a smaller set of logs with only meaningful, notable messages being shown.||Success/failure notifications, task status and progression messages.|
|Debug||This setting will show all that standard shows with additional messages for lower level details that professionals may care about.||Generated queries/statements, performance metrics, additional connection information.|
The Logging Batch Size determines the rate at which logs are submitted to the Loome Integrate Online API from the Agent. By default, the agent will submit logs in batches of 5. If there is a job which creates a large amount of logs (>100 pages worth) it’s advised that this value is increased so that less load is put on your tenant.
Increasing the batch size will slow down the rate at which realtime logging occurs in the job execution screen, however this does not slowdown the performance of the job execution itself.
The email notification rule can be used to configure job driven email notifications.
Currently Loome Integrate Online supports 3 different levels of email notifications.
|Rule||On Success||On Failure|
|No Email||No emails will be sent to the provided recipients.||No emails will be sent to the provided recipients.|
|Notify on Success or Failure||Emails will be sent to the provided recipients.||No emails will be sent to the provided recipients.|
|Notify on Failure||No emails will be sent to the provided recipients.||Emails will be sent to the provided recipients.|
Once you select a valid rule, you can enter a comma separated list of recipients who will receive the email notifications.
Note that there is currently no guarantee that Loome Integrate’s emailing system will bypass spam filters so you will need to configure exceptions in some instances.
The retry count determines the number of times a job will be repeated if it fails on its first execution.
If you choose a number here and your job fails when you first run it, the job will automatically restart the task in the same execution. It will repeat the job the amount of times you have selected, depending on whether it completes successfully or fails (further explained below).
If successful, it will not need to repeat again so it will complete the job and its status will be noted as ‘Warning’ as shown in the image below. This job status of ‘Warning’ still means that a job was successful, the status only differs from the ‘Successful’ status to notify users that a job passed successfully due to the retry setting on repeated attempt.
If the next attempt fails, it will repeat for the amount of times you have selected as the retry count number.
For example, if I chose three retry attempts for this job, and the job failed its first attempt but it completed successfully on its second attempt, it will have run a total of two times. But if it had continued to fail on that second attempt, the job will repeat again and run a total of four times.
Using the ‘Depends On’ section, you can select the jobs that this job will be dependent on. If it is dependent on another job, that job’s last execution will need to be successful so that this job can run.
If you want this new job to be dependent on another, check the box next to each applicable job name.
You can also choose whether a dependent job should still run if the job it is dependent on failed when it was last executed.
This behaviour is not enforced by default, you will need to set ‘Run this Job on Dependent Failure?’ to ‘Yes’ in order to utilize job dependencies.
If you have chosen for a job to be dependent on a job that has the Retry Count enabled, the dependent job will wait for all necessary re-attempts to complete and will run if the first or a subsequent attempt was successful.
You can also make a job from one project dependent on a job from another project using cross project job dependency.
While viewing a job in a project, click on the Job Dependency button.
Browse jobs from all projects and select the jobs that this job will be dependent on. All your projects will be displayed on the left, and the jobs relevant to the project will be displayed on the right.
From here you can also view any existing dependencies.
Select whether this job will run on dependent failure.
Running a job that is dependent on jobs in other projects will not cause those jobs to also run. It will only run this job, and its outcome will depend on the status of the jobs it is dependent on.