| Menu | Terminal Administration -> Communication Details -> Job History. |
The Job History page displays historical information about executed jobs, e.g. all failed jobs for a specific terminal or all completed Submit Collections commands.
| Note: This page uses Enforced filtering. You must select a Date Changed before you can display the list. Select the period you want to see. This is default set to Dynamic Time Span – Last 24 Hours. |
Click the 
icon to go to the Terminal Jobs tab on the Terminal Details page, where the status of individual jobs applied to the chosen terminal is shown.
Click the plus 
symbol to display detailed information about each terminal command included in a job, e.g. the Submit Statistics job.
The following table explains the items on the page:
List item |
Explanation |
|---|---|
Terminal – Terminal ID. |
Shows the terminals id. Must be unique within the company. |
Name. |
Shows the command telling the terminal (CWT) what to do. For example, the SubmitCollections command tells the terminal to send information about completed collections (since this data was last submitted). |
Execution Status. |
Shows the status of the job: Completed, Re-running or failed. Re-running indicates that the terminal keeps trying to collect the job and run the related command(s). A common case for re-running occurs when a collection job is started but no collection data is available due to no physical collection has been made. This is a typical scenario on an MP 104. |
Date Changed. |
Date and time, in terminal’s local time, when the execution status record was changed. |
One Time Job. |
Check box selected means that the job is a one-time job, not a recurring job. |
Is Abort Job. |
Check box selected means that the job is an Abort-job. |
Parent Guid. |
Shows the parent node GUID if there is any. |
Terminal. |
Shows the terminals GUID. |
