| Table of Contents |
|---|
Monitoring Jobs
Viewing Running Jobs
To see all currently running jobs, go to Admin >> Manage Jobs and Sets >> Monitor Jobs. There are three tabs: Scheduled, Running, and History.
...
At the right is the row action item list icon (...), where you can Abort your job if you realize you need to change something, it isn't running properly, or any other reason.
Viewing Completed Jobs
On the Monitor jobs screen, we can see a list of completed jobs on the History tab.
...
From here, you can see the status of the job and access a more complete report about the job. Let’s look at those, and also how to troubleshoot common issues.
Job Reports and Troubleshooting Error Messages
There are several possible statuses in the job status column:
...
Counters: These are details that usually count how many records were changed in which ways by the job. Again, if you don't see a parameter that you had intended to change in this list, it means you probably forgot to tick the box to the left of the parameter to indicate to Alma that you wanted to change that field. You'll need to re-run the job on the same set of records, this time changing just that one parameter. Definitely get in the habit of reviewing the Counters after you run a job to make sure everything changed as intended.
For some jobs, there will be a link to download a more detailed report to Excel, containing information about each record and the changes made to it or what errors came up for that record. For others, the number next to each counter may be a blue link to more information.
Other Sections: More complex jobs may have several more sections to review the outcome of the job. The first few times you run a new job, review the Report screen to see what information about the job is available here.
Errors, Warnings, and Fails
If your job Completed with errors, Completed with warnings, or Failed to run, it’s important to review what didn’t work and why so you can change your set or your parameters and try again.
...
It is LTS's experience that user-initiated jobs don't Complete with warnings. If your job does, please contact LTS Support immediately so they can help diagnose what's happened.
Checking results
It's best to check a few of the results to make sure your job worked as expected. If you used a logical set, it may not be empty. Check the export you made of the set prior to running the job to find some example records.
Next Required Reading
Restoring Records Removed or Changed by Jobs