Monitoring Outbound Jobs

Staff users can review and monitor in-progress and past job runs.

Viewing past job runs

To view the past runs for a particular job, select the Actions menu, and select View Job History.

In the Job History, the following details are available:

When the job ran
How long it took
How many records were sent (if delta hashing is enabled, the count reflects the number after the hashing occurred)
The status of the job

Viewing an individual job run

Select the Details button to view a job's full run log.

The History Details will display a summary of the job, including the full execution log.

If the job is running, a progress bar at the top displays the overall estimated progress of the job.

Note: If you view a job's execution log before it is finished, the screen will update in real-time. Do not refresh the browser.

Canceling a job

To cancel the job, select the Cancel Job button.

Note: The job may not cancel right away. The job engine only periodically checks for a cancellation request, and if it is currently executing one of its sub-processes, it may need to complete that process before it receives the cancellation request.

Force Stopping an Orphaned Job

In certain cases, a job may terminate unexpectedly. If this happens, new text will not be added to the execution log for a long period of time (more than 1 hour). After about three hours, if the iTransfer host does not receive any updates from the job, it is considered orphaned.

Select the Force Stop Job button to close out the job record and mark it as cancelled. Treat this job as if it failed. To re-execute the job, start a new ad-hoc run, or wait for the next scheduled time.

Understanding the Execution Logs

The Execution Log is the full log output of the job, including any status messages and errors that occurred.

The Execution Log consists of the following sections:

Job Initialization
Data Retrieval (optional, if Data Source is set to None)
Delta Hashing (optional)
Transmission Step(s)
Cleanup and Email Notifications