Skip to main content
Version: FCP 25.11

Job Monitoring

This guide explains how to use the Job List in Desktop Portal to view jobs submitted through the scheduler, including status, submission time, runtime, and resource usage.

Prerequisites​

  • You have a Desktop Portal account and are logged in.
  • You have submitted jobs via the scheduler.

Open the Job List​

  1. Log in to Desktop Portal.
  2. On the Cloud Workbench page, click Job List.

Fields in the Job List​

The Job List page displays the following fields:

  • Job ID: unique identifier of the job.
  • Job name: name of the job.
  • User: username who submitted the job.
  • Status: current job status (queued/waiting, running, completed, failed, and so on).
  • Execution host: the physical host or node where the job runs.
  • Partition: compute partition or queue name.
  • Nodes requested: number of nodes requested by the job.
  • Memory requested: memory requested by the job.
  • CPUs requested: number of CPU cores requested by the job.
  • Project: project name or ID.
  • CPU time used: CPU time consumed by the job.
  • Elapsed time: total runtime from start to end.
  • CPU used/requested: ratio between CPU time used and CPU requested time.
  • Wait time: time from submission to start.
  • Submitted at: submission time.
  • Started at: start time.
  • Finished at: end time.
  • Exit code: exit code after completion.
  • Exit signal: signal value for job termination (if applicable).

Filtering and Sorting​

  • Quick filter tabs
    • Queued & Running: show jobs that are queued or currently running.
    • Completed: show finished jobs (both success and failure).
    • All: show all jobs (default view).
  • Filter: filter by status, submission time, job name, user, queue, project, execution host, and more.
  • Sort: click table headers to sort by job ID, submitted/started/finished time, runtime, CPU time used, elapsed time, wait time, and more.

FAQs​

  • Can't view the Job List:
    • Confirm you have submitted jobs via the scheduler.
    • Check your network connectivity.
  • Job status looks abnormal:
    • Check job logs to identify the issue.
    • Contact your administrator to check scheduler configuration and runtime status.
  • Job stays in "waiting/queued" for a long time:
    • Check whether queue resources are sufficient.
    • Contact your administrator to adjust job priority or resource allocation policy.