Docs
Search K

Appearance

Minute Insights ​

Job History ​

MinuteView keeps record of executed Jobs via the Job History feature found within the Minute Insights module.

Job History

Use the filter options found within the Menu Bar to focus on the Jobs that matter.

Number of Recent Records ​

Filter down the Job History to show the desired range.

  • Today
  • Most recent 10, 100, 500, 1000, 10000 jobs.

Status ​

Select a status from the pick-list to filter Job entries, useful for isolating problematic Jobs.

  • ALL
  • FAIL
  • COMPLETE
  • ABORT

View Enterprise 🔒 ​

The primary View will be displayed by default, as configured within Report View . Displaying other configured views is available under a MinuteView Enterprise Plan.

A text based search tool that allows for the complete searching through all Job History Fields.

The matched return records are limited by the Number of recent Records field value. Increase the value to 10000 to cater for a broader search across more Jobs.

Job History Fields ​

ID ​

The unique ID of the processed Job.

Log Time ​

The time on the MinuteView server at the point of Job execution.

Name ​

The file name and extension of the target file processed by the Job.

Job Status ​

The Job status is a clickable hyperlink that displays the log file associated with the processed Job.

Statuses include;

  • COMPLETE
  • ABORT
  • FAIL

Error Title ​

If the Job Status is either FAIL or ABORT, the errors title will be displayed. Common area types include;

CHANGE STATE ERROR
FILE IS CHECKED OUT

Job Name ​

The name of the Job processed. Jobs can be configured via Minute Creator

Job Submitted By ​

The name of the Vault account logged into the Job Processor whilst that Job was executed.

Processor Name ​

The Computer Name / Hostname of the Job Processor that executed the queued Job.

Job Description ​

A description of the executed job, typically a concatenation of the Job name followed by the resulting generated file.

Jobs submitted via Minute Controller Queue Jobs are denoted as MANUALLY ADDED FILE and ADDED TO QUEUE.

Job Error ​

Provides more comprehensive detail than the Error Title field when a Job fails upon execution. The Job Status field may be clicked to expand the entire log to provide comprehensive details regarding the failed job and error encountered.

Example Job Errors ​

Errors aim to be descriptive of the problem encountered, below is are examples of a common errors:

File was checked out preventing Job to process ​

ABORT: TITLE: FILE IS CHECKED OUT: FULL MSG: CAD FILE: Bench Vice Detail.dwg IS CHECKED OUT TO USER: Administrator CHECKOUT
TIME: 2024-02-08 12:37:51 PM, PLEASE CHECK IN OR UNDO CHECKOUT AND RE-SUBMIT - (WAITED 10000)

From the above example, the Job attempted to process a file Bench Vice Detail.dwg whilst it was checked out to the user Administrator. That itself did not fail the Job, as the Job further waited for 10,000 milliseconds (10 seconds) as per the Checkout Retry Pause timeout delay before attempting to process the file one final time, after of which returned the Job fail as the file was still checked out to the Administrator.

Job failed to update PDF Lifecycle State ​

FAIL: TITLE: CHANGE STATE ERROR: FULL MSG: FAILED TO UPDATE PDF LIFECYCLE DEFINITION - PDF OVERRIDE Basic Release Process: SOMETHING
WENT WRONG DURING UPDATE LIFECYCLE DEFINITION: 3110

In the error above, the Job failed and returned this error due to a failed attempt of assigning the "Released" state to a PDF file within an Office Category, under the Basic Release Process Lifecycle.

Upon checking the Vault Category and Lifecycle configurations, a simple mistake has been made - and the Job should have been configured with the Simple Release Process and not the Basic Release Process. Upon reviewing this error, updating the Job in Minute Creator, and then re-submitting the job via the Vault Job Queue, the Job was successfully processed.

Tentech 2024