Module: Processing

Path: Processing > Process History

Topic: Process History

Version(s):  All

Editions: All

---

What Is Process History

Process History is a display of all jobs that have processed or are currently processing in your system. This is a convenient screen to help you review job logs of multiple jobs and download files if available.

---

Making The Connection

Where Will I See This Within OLX?

You can get to the Process History by navigating to Processing > Process History from the menu bar at the top of your instance.

What Reports Can Be Pulled?

1. Schedule History Report
   
2. Schedule List Report

What Imports/Exports Relate to Process History?

At this time there are no imports or exports related to Process History.

---

How To

Tool Bar

Utilizing the buttons on the tool bar  you can:

Go back to the previous screen 

Print 

Minimize module 

1. Ended Date - Server date and time the job ended
2. Instance ID - Unique ID for that one instance of the job
   
3. Job Name - If a scheduled job this will be the name of the schedule, if a manual run (-UI) this will be the name of the spec being used
   
4. Job Type
   
1. Module Job Types:
   
1. Commission Processing
2. Commit Inventory
3. Common Reports
4. Continuity Processing
5. Create Payment Batch
6. Customer DeDupe
7. Generic Export
8. Generic Import
9. Generic Process Job
10. Media Buyer Call Report
11. Media Source Job
12. Notification Delivery
13. Payment Processing
14. Payroll Processing
15. Prepayment Processing
16. Process Alert
17. Reconcile PIA Job
2. System Job Types:
   
1. Auths Without Orders
2. Data Retention
3. Delivery Validation
4. Fetch CS Emails
5. Inventory Back Order Release
6. OrderMetrix Calculation
7. Purge CVV
8. System:Cleanup Temp Tables
5. Started Date - Server date and time the job began
   
6. Status
   
1. Succeeded - The job was able to complete processing.
   
2. Failed - The job was unable to complete processing.
   
3. Cancelled - The job was cancelled manually prior to completion.
   
4. SysCancelled - The job was cancelled by the system.
   
1. This may happen for various reasons. If there are multiple jobs that are attempting to run that are utilizing too many system resources one of the jobs may be cancelled to make it possible for the other job to run.
   
5. Running - The job is currently in process

Add additional filters by click the Add button 

Apply the filtered selections by clicking Apply Filter 

Remove the filtered selections by clicking Remove Filter 

To show system jobs that run in the background (these are jobs that are required to maintain a healthy system and are activated on the backend) check Show System Jobs

If you want to see only the processes that have failed check Show Failed Only

Create Schedule

1. Automated Schedule

How To Read Data

Succeeded does NOT mean there are no errors in the job log. It may be necessary to review the job log to investigate concerns. 

Jobs should not run longer than 2 hours under normal circumstances. If you have a job that has been running 2+ hours, please open a ticket

You may find it helpful to utilize the Ctrl+f search feature if you are looking for specific information within a job or multiple jobs. Just make sure to have all the jobs to be reviewed expanded.

1. Beginning of output - 
   
1. steps taken to begin process
   
1. load
   
2. configure
   
3. run
   
4. review 
2. End of output -
   
1. will give a brief summary of the results of data that was processed
2. link for download to additional information passed with the spec being used
   
3. any errors
4. status of job
   
1. success
   
2. failed