Management of the job instances and provisioning sequences

To access job instance and provisioning sequence management, go to the “Jobs” menu:

You will be taken to the provisioning job instance tracking page with a preloaded list of existing instances.

Viewing a job instance

A pagination system is set up with a default display of 10 results.

It is possible to change the number of results to display and navigate between the different pages.

For each job instance listed, depending on the permissions of the connected user, the following action buttons may be available:

• : allows you to view the details of a job instance, i.e., the statuses of the various sequence instances that make up the job.

For each sequence instance, you can see the start and end dates as well as the status of the sequence.

• : allows you to delete a job instance.

• : allows you to archive a job instance (it is still present in the database but no longer visible on the screen).

Acting on a job instance when a threshold is reached

In order to secure the provisioning sequences, both upstream and downstream, thresholds are configured for each import. If the threshold is reached for one of the actions (creation, modification, or deletion), the sequence is stopped and no writes are made to the target repository.

If the sequence was executed via a provisioning job, i.e., via the SIP API, then it is possible to view, validate, or block the sequence from the job instance management interface.

Open the job instance that has the “Threshold” status in view mode. You can view the details of the sequence that has been blocked by a threshold.

To validate a job at threshold, click on the “” button. At this stage, the sequence that was stopped by the threshold is validated but not restarted. You must restart the job manually by clicking on the “” button or via the API.

To cancel a job at threshold, click on the “” button. The blocked sequence and subsequent sequences will be canceled.