Table 6. Job Manager Instance Properties
|
|
JobID |
ID of the job associated with this instance. |
InstanceID |
Unique ID of this specific instance of the Job. |
Status |
The Status of the job instance can be one of the following: |
|
|
This is the same for iBot jobs and Script Jobs. If the instance is running, the status is running. |
|
|
iBot: The iBot instance is set to completed if we successfully deliver to all delivery devices of the iBot. |
Script: This is set according to the Severity property in the script. Refer to Table 18. |
|
|
iBot: The iBot instance is set to failed if we were not able to successfully deliver to any of the delivery devices of the iBot. |
Script: This is set according to the Severity property in the script. Refer to Table 18. |
|
|
iBot: The iBot instance is set to Warning if we were able to successfully deliver to some of the delivery devices but not all. |
Script: This is set according to the Severity property in the script. Refer to Table 18. |
|
|
Canceling any instance from the job manager will set the status to cancelled. |
|
|
If the job has a maximum run time, and the running time of the instance exceeds this, then the status of the instance will be set to timed out. |
Begin Time |
The day and time the scheduler initiated the job instance. |
End Time |
The day and time the job scheduler completed the job instance. |
ExitCode |
Exit code of the instance. Depending on the job type, this code can be interpreted differently. |
|
|
The ExitCode of an instance is set to the number of successful deliveries. The count corresponds to the number of successful deliveries to devices, and there may be more than one device for each recipient of an iBot. |
|
|
The ExitCode of an instance is set according to the ExitCode property in the script. The default is 0 (zero). Refer to Table 18. |
Message |
Text message containing any error information of the instance, warnings, or general messages about the instance execution. |
