Skip to content

Job Runs ​

Use Reporting → Job Runs to investigate endpoint and infrastructure executions across jobs. Job Operator can review and abort runs.

In endpoint and infrastructure job trees, the hourglass counts queued runs. The spinner counts other active runs, including runs that are cancelling or disconnected. A job can show both counts when it has multiple runs.

Run Details ​

Find the run by job, endpoint, status, or time, then inspect the failed or delayed step. Select View output in the step details to inspect captured output, and review its artifacts before retrying. For infrastructure work, use the journal to follow execution on the Runner; for endpoint jobs, check whether one device or the entire target set is affected.

Captured live output can be incomplete even when an endpoint task succeeds. Check the task result and collected artifacts before deciding to retry.

Folder synchronization waits for pending malware scans and for every selected file to become available on the endpoint's assigned Cache. Open the step details to follow each file's cache progress. If preparation fails, review the reported file and error before retrying the run.

For infrastructure runs with test reports, open Tests to investigate failed tests or Reports to inspect collection problems.

Infrastructure runs can also display named HTML report tabs.

See Jobs for execution settings and Infrastructure Jobs for journal and retention guidance.

Abort Active Work ​

Use Abort job run to stop pending work and request cancellation of an active task. Allow time for active work to stop and for configured Cleanup to finish.

Aborting during Cleanup lets it finish. Once cancellation is pending for all remaining targets, use Force abort job run to abandon remaining cleanup. Work already accepted by an external system may continue, so inspect the outcome before starting another run. Completed targets retain their outcomes.

Cancellation history records who requested normal or forced cancellation and when. Review Output or target history for cleanup outcomes.

A finished run can still need Runner recovery when stopping execution or releasing its workspace could not be confirmed. Use Retry Runner recovery when offered; the completed run result is preserved.

You can abort disconnected infrastructure runs and endpoint runs, including individual endpoint targets. Cancellation can remain pending until the Runner or Agent reconnects.

To stop a job on one endpoint, open its context menu in the endpoint's Jobs tab and choose Abort. The confirmation identifies the endpoint.

In either job library, open a job's tree context menu and choose Abort job to stop its active runs. The confirmation identifies the affected runs; runs started afterward are not included.

PXE configuration publishing waits for confirmation from the assigned net node before the job continues. Aborting the job withdraws its boot configuration when the net node can apply the update; delayed confirmations do not restart aborted work.

Power on results ​

A successful power-on request does not establish that an endpoint's Agent has connected. Inspect the method and outcome, and use a separate wait step when later work requires a connected device. See Powering on endpoints.