Administration

Background jobs and job insight

Check scheduled tasks, start them by hand and read their output live or afterwards.

EasyUC · Version 4.8.7

In EasyUC: Administration → System & Operations → Background Jobs

What it is for

Many processes in EasyUC run on a schedule in the background: reconciliations with the CUCM, the inventory for live monitoring, retrieval of the CUCM audit log, deletion of expired audit log entries and others. The Background Jobs page shows all scheduled jobs with schedule, last run and next run.

You need the page when data in the interface looks outdated or an automatic function does not take effect. The job insight lets you read the output of the last run or watch a running job live. You can also start a job by hand immediately instead of waiting for the next slot.

The page shows scheduled jobs only. One-off tasks such as a call diagnosis or a log collection have their own status in the respective function.

Prerequisites

Access to the menu area Administration → System & Operations, or to System in the ACD and Teams areas.
Run Now is carried out for administrators only.
The background job service is running. Otherwise the list stays empty or the times do not change.

Step by step: check a job

Open Administration → System & Operations → Background Jobs.
Find the job in the Name column.
Compare Schedule, Last Run and Next Run At. A job that runs hourly according to its schedule but shows "never" under Last Run is conspicuous.
In the row, click Last Logs. The dialog shows the output of the last run.
On the Logs tab, read the lines from top to bottom. Look for lines with the level CRITICAL.
If required, switch to the Raw Logs tab to see the complete raw data of every line.
Close the dialog with Close.

Step by step: start a job immediately and follow it live

In the row of the job, click Run Now.
Confirm the prompt Do you want to run this job now?.
The Next Run At column now shows Running... in green.
In the same row, click Live Logs. The heading shows "[ running ]", and the output lines appear below it while the job works.
After the job has ended, the column shows the next slot again. You then find the output under Last Logs.

Fields and options

Fields and options
Field / action	Meaning and use
Name	Name of the job.
Schedule	Schedule of the job as stored in the system.
Last Run	Time of the last run, or "never".
Next Run At	Time of the next scheduled run. Running... during execution.
Run Now	Starts the job immediately. Disabled while the job is running or is due to start in less than a minute anyway.
Last Logs	Output of the last completed run.
Live Logs	Output of the job currently running, in real time.

How to read the log output

How to read the log output
Field / action	Meaning and use
First column	Time of the line.
Second column	Level of the message. `NOTICE` and `CRITICAL` are highlighted in colour. `CRITICAL` marks an error in the run.
Third column	Memory usage of the job at the time of the line, or a dash.
Fourth column	Message text.
Live logs heading	"[ running ]" during execution, otherwise "[ next run at: … ]".
Times	All times are shown without a date. A run from yesterday cannot be recognised by the time alone.

Check the result and narrow down errors

A healthy job has a current Last Run, a Next Run At in the future and no CRITICAL lines in Last Logs.
"the job will start in less than 1 minute": Run Now is disabled because the scheduled run is imminent. Wait for the run.
If nothing happens after Run Now, the job is already running or your account is not an administrator. A second parallel run is not started.
If the times in the list no longer change, the background job service is not working. Check it in the EasyUC Manager.
If the log shows an AXL or sign-in error towards the CUCM, check the CUCM connection first. Fix the cause before starting the job again.
What a job changed in the system is recorded in the audit log with the source Background job.
For support cases, copy the affected lines from Raw Logs. Remove personal data first.