5 Run jobs and check history
This section contains the following topics:
View and edit your subscriptions to job status notifications
You can subscribe to receive email notifications about the completion status of jobs.
To subscribe or unsubscribe to notifications for other studies, select a different study and repeat the steps in this procedure.
Parent topic: Run jobs and check history
Run transformations and view run history
Parent topic: Run jobs and check history
View transformation job history
As described in Run transformations and view run history, you access transformation through the Transformations tab on the Home page. Transformations are displayed by the name of their target clinical data model.
-
To view table transformations, click a transformation's node.
-
To view run history and pending jobs, select a transformation in the upper pane.
-
To view log files, click the icon in the column for the type of job:
-
Log: The most recent manually submitted job.
-
Triggered Job Log: The most recent triggered job.
-
Install Job Log: The most recent installation of the transformation.
-
Parent topic: Run transformations and view run history
Run a transformation
To run or schedule a transformation:
Click the Refresh icon for an update to the Job Status.
Parent topic: Run transformations and view run history
Cancel a transformation job
As described in Run a transformation, you access transformation through the Transformations tab on the Home page. Select a transformation in the Run History pane and click:
-
Cancel Job to cancel the currently running or next pending job.
-
Cancel All Jobs to cancel the currently running or next pending job and all future jobs in the schedule for the selected transformation. Available only for scheduled jobs.
Note:
If there is an immediate or deferred job for the same transformation, or another schedule for the same transformation, those jobs are not affected.
-
Cancel Triggered Job to cancel the currently running or pending job. Available only for jobs that are set up to be triggered by another job.
Parent topic: Run transformations and view run history
Run validation check batches and view run history
Parent topic: Run jobs and check history
Run a validation check batch
You must run validation checks as a batch.
Parent topic: Run validation check batches and view run history
Cancel a validation check batch job
As described in Run a validation check batch, you access validation check batches through the Validation Checks tab on the Home page. Select a validation check batch in the Run History table and click:
-
Cancel Job to cancel the currently running or next pending job.
-
Cancel All Jobs to cancel the currently running or next pending job and all future jobs in the schedule for the selected validation check batch (available only for scheduled jobs).
Note:
Cancelling a job does not affect an immediate or deferred job for the same batch or another schedule for the same batch.
-
Cancel Triggered Job to cancel the currently running or pending job (available for jobs triggered by another job).
Parent topic: Run validation check batches and view run history
Reprocess discrepancies that failed to be sent to InForm
Validation checks with an Initial Action of Send to InForm immediately send discrepancies they create to InForm as queries. To check the status of this operation:
Parent topic: Run jobs and check history
Check if data files loaded
The section contains the following topics:
Parent topic: Run jobs and check history
View data load history
Parent topic: Check if data files loaded
Statuses for uncompleted jobs
As described in View data load history, you can view data load history through the Data Loads tab on the Home page. For incomplete jobs, the system displays the job's current status. Click the Refresh icon to update the table.
-
Pending: The job has not yet started running.
-
Started: The job has begun pre-processing.
-
Executing: The Program has connected to the database and is running.
-
Finalizing: The job has begun post-processing.
-
Aborted: The job has been manually stopped while underway.
-
On Hold: The job is waiting for the quiesce process to complete for the clinical data model work area.
-
Expired: The system removed the job from the queue after the timeout interval passed.
-
Duplicate: The job is a duplicate of another job; the currency of the source data, parameter values, and executable instance version are the same. The system does not rerun the job unless the person submitting the job chooses to force reexecution.
Parent topic: View data load history
Review data load errors (optional)
To review data load errors:
- Click
Home in the navigation bar and select a study from the Studies
panel.
Note:
For details on selecting a study, see Select a study. - Click the Data Loads tab to open a table with details on files that loaded into the selected study.
-
Open a file in one of the following columns:
-
Last Load Results: Contains the results of the most recent data load. This file is produced whether the data load is successful or failed.
-
View Output:: Produced during a data load (the SQL*Loader log). This file is produced whether the data load is successful or failed.
-
View Error File: Created when a text file for a data load contains more fields than there are columns in the table you're loading the data into. This file is produced for failed data loads only.
Tip:
This column is typically empty.
-
View Comprehensive Error Report: The error log includes a list of the specific data record and field from the file that caused the error. This file is produced for failed data loads only.
-
Parent topic: Check if data files loaded
FAQs
Parent topic: Run jobs and check history
Why can't I see a job that ran a while ago?
By default you can see only recent jobs. To see a job that happened longer ago, click the View Full Job History icon.
To change back, click the View Recent Jobs Only icon.
This applies to the Home page Data Loads tab and the Run History pane of the Transformations and Validation Checks tab.
Parent topic: FAQs
Why am I seeing a Diagnostics Icon?
The icon indicates that your administrator is running diagnostics for troubleshooting purposes. Performance may be slower than usual.
Parent topic: FAQs