Job Late Event
When the deadline time instructions of the monitored job is exceeded, and if the job is not yet started or still in progress, it triggers an event.
Overview
You can configure the event conditions with late job statuses KILL or CONTINUE or both. You can customize both mandatory and optional attribute filters to define specific conditions to trigger an event.
The mandatory attribute filters that you must provide to configure the event are:
-
- Workstation
- Specify the workstation of the job stream that contains the job to be monitored. This detail must be preceded by the workstation folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
-
- Job stream
- Specify the job stream that contains the job to be monitored. This detail must be preceded by the job stream folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
-
- Job
- Specify the name of the job that is monitored for a change in its status. When the specified status or statuses for the job is reached, it satisfies the condition. If you do not specify any value for internal or external status, whenever the job changes its status the filter is considered satisfied. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
The optional attribute filters that you can add to trigger the event for specific
scenarios are:
-
- Job workstation
- Specify the workstation where the job to be monitored runs. This detail must be preceded by the workstation folder details. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are permitted.
-
- Priority
- Specify the priority of the job. You can specify any value between 0-101. If you add a value, the change in status of the monitored job only with that priority satisfies the condition. The supported value type is nonnegativeinteger and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
-
- Late action
- You can add the expected late action for the monitored job to
trigger an event. The valid attribute values are
KILL
andContinue
. If you do not specify any value, when the job status change to either KILL or CONTINUE, it satisfies the condition. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
-
- Recoverable
- This optional attribute is only valid if the job you want to monitor has recovery or rerun option. The supported value type is boolean and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted.
-
- Output conditions
- You can specify the name of the output conditions of the monitored job, if any exist. Make sure to add only those output conditions that are satisfied for the job. The supported value type is string and for available operators see Event driven orchestration configuration attributes. Wildcard characters are not permitted. You can add single or multiple values and if any one is matched, the filter is considered satisfied.