DCIM creates jobs when an operation needs time, an agent, a server reboot, a BMC action or a switch action. Provisioning, rescue, discovery, diagnostics, diskwipe, power control, remote console actions and switch sync all use jobs.
Logs are different. A log is an activity record: it helps you understand who ran an action, when it happened, which API path was used and what target was affected. When troubleshooting, start with the job for the operation itself, then use logs to understand the surrounding activity.
Where to find jobs
Admin users can open
System > Jobs to see jobs across the platform. Server and switch detail pages also show recent jobs related to that device.Access portal users can open
Jobs to follow operations related to their visible servers. They do not see global infrastructure jobs outside their access scope.Job list
The list shows the job ID, target server or switch, job type, profile, agent, status, requester and timestamps. Use this view when you need to answer what is running now or what failed recently.
Filters
Admin filters can narrow jobs by status, type, server, switch, agent, profile or ISO. Access portal jobs are scoped to the user and can be filtered by status, type, server, agent and profile.
Job status
Status tells you where the operation is in its lifecycle. Active jobs update while the job detail page is open.
QUEUED
The job was created and is waiting for the worker or agent to pick it up. If it stays queued for too long, check the assigned agent and the platform workers.
PENDING
The job is preparing to run. This can include reserving PXE data, preparing metadata or waiting for the next execution step.
RUNNING
The job is currently being executed. Open the job detail and watch events, progress and the error section if the operation stops.
COMPLETED
The job finished successfully. Review the result or metadata only if you need to confirm what the operation changed.
FAILED
The job did not finish successfully. Open the detail page and read the error message first, then review events and metadata for the failing step.
CANCELLED
The job was stopped before completion. For provisioning jobs, cancellation also removes PXE reservations and returns the server to its default boot flow.
Job detail
Open a job when the list is not enough. The detail page shows the target, type, agent, requester, timing, metadata, error message, steps, events and related scripts.
Overview
Overview identifies the server or switch, selected profile, hostname, disk layout, assigned agent and who requested the operation. Use it to confirm that the job is attached to the expected device and datacenter.
Error
If the job failed, read the error section before changing settings. It is the shortest explanation of why the job stopped.
Steps
Workflow jobs can contain steps. For example, a provisioning workflow may run a diskwipe step and then an install step. Open the failing step when the workflow error is not specific enough.
Events
Events show progress inside the job. They are useful when the job is still running or when you need to know exactly which part failed.
Metadata and scripts
Metadata can contain structured details produced by the job. Scripts show the reusable post-install scripts attached to a provisioning job.
Cancel or delete jobs
Job actions depend on permissions and status. If an action is not visible, the job type, job state or your permission does not allow it.
Cancel Job
Cancellation is available for active provisioning jobs such as
REINSTALL, RESCUE, DISCOVERY and DISKWIPE while they are queued, pending or running.Use it when the operation was started by mistake or when the server should stop following the PXE flow. Cancellation removes PXE reservations and reboots the server back to its default boot flow.
Delete
Admin users with job management permission can delete jobs after they are
COMPLETED, FAILED or CANCELLED. Delete only when the history is no longer useful for operations or support.Where to find logs
Admin users can open
System > Logs to review platform activity. Access portal users can open Logs to review activity related to their servers and access.Dashboard logs are not the same as host service logs. If the dashboard, API or proxy is unhealthy, use the host commands in Troubleshooting instead.
Log list
The list shows created time, target, executor, HTTP method, level, path, category and message. Click a log to open the drawer with the full details.
Log details
The drawer shows the timestamp, level, method, path, IP address, category, executor, target, message and metadata. Metadata is useful when the message is short but the operation stored additional context.
Log filters and cleanup
Use filters when investigating a specific change instead of reading the full log list from newest to oldest.
Level
Use
INFO for normal activity, WARN for warnings and ERROR for failed or unexpected operations.Method, category and date
Method helps isolate reads, creates, updates and deletes. Category groups logs by area of the system. Date range is useful when you know when the change happened.
Target and executor
Admin logs can also be filtered by target ID, account ID, user ID and profile. Use these filters when support asks for activity around one object or one user.
Delete logs
Users with log management permission can delete one log, all logs or a filtered set by level, method or category. Deletion cannot be undone, so keep logs while investigating incidents, provisioning issues or account activity.
Troubleshooting order
For a failed operation, open the job first and read the error. Then check events, steps and metadata. If you still need context, open logs and filter by the same time window, target or executor.
If the job depends on an agent and the job stays queued, pending or fails early, check the agent status in Agents.
Jobs and logs video
