My Jobs
the jobs table, job states, cancelling, output files, auto-refresh
Viewing and Filtering Jobs
The Jobs page shows all jobs associated with your account. Open it by clicking Jobs in the navbar.
Tabs
- My Active Jobs — jobs submitted under your username, both active and recently completed.
- Cluster Queue — every job currently on the cluster, visible to staff only.
- Job Search — search historical and active jobs by Job ID, Name, User, State, or Partition. Enter at least one filter and click Search.
Job list columns
| Column | What it shows |
|---|---|
| Job ID | Slurm job ID. Array jobs show as jobid_taskid. |
| Name | The job name you entered on the submission form. |
| Partition | The queue the job was submitted to. |
| State | Current job state. See the Job States page for the full list. |
| Nodes | Number of nodes allocated. |
| CPUs | Total CPU cores allocated. |
| Time | Elapsed wall-clock time vs. the time limit. |
| Submit time | When the job was submitted. |
Filtering jobs
On the My Active Jobs and Cluster Queue tabs, use the search bar above the job list to filter by job name, job ID, partition, or state — the filter applies instantly as you type. For deeper historical searches with dedicated fields per criterion, use the Job Search tab instead.
Job detail panel
Click any row to open the detail panel on the right. It shows the full resource allocation, the node the job was submitted from, exit code, and action buttons (output, cancel). The panel polls for state updates every 5 seconds while the job is running.
Job States
Every Slurm job moves through a series of states from submission to completion. The current state is shown in the State column on the Jobs page.
Common states
| State | Meaning |
|---|---|
| PENDING | Waiting in the queue. The job has not started yet. See below for common reasons. |
| RUNNING | Executing on a compute node. |
| COMPLETING | The job has finished but Slurm is still cleaning up (collecting exit codes, releasing nodes). Transient — usually lasts a few seconds. |
| COMPLETED | Finished successfully (exit code 0). |
| FAILED | Finished with a non-zero exit code. Check the output and error files for details. |
| CANCELLED | Cancelled by the user or an administrator before or during execution. |
| TIMEOUT | Reached the time limit and was killed by Slurm. |
| OUT_OF_MEMORY | Exceeded the memory limit and was killed. Resubmit with a higher memory allocation. |
| NODE_FAIL | The allocated node failed during the job. Resubmit; consider using Exclude nodes to avoid the failed node. |
Why is my job PENDING?
A pending job is waiting for one of the following reasons:
- Resources — not enough free CPUs, memory, or nodes in the partition right now. The job will start automatically when resources become available.
- Priority — other jobs have higher fair-share priority. Your priority increases the longer you wait.
- QOS or account limits — you have reached a per-user or per-account job or CPU limit set by the QOS. Wait for a running job to finish.
- Time limit — your requested time limit exceeds the partition maximum. Lower the time limit or switch partitions.
Terminal states
COMPLETED, FAILED, CANCELLED, TIMEOUT, and OUT_OF_MEMORY are terminal — the job will not change state again. The detail panel stops polling once a terminal state is detected.
Cancelling a Job
You can cancel any of your jobs that are in PENDING or RUNNING state. Cancelling a running job stops it immediately — any output written so far is kept, but the job will not complete.
How to cancel
- Go to the Jobs page.
- Click the job row to open the detail panel.
- Click Cancel Job.
- Confirm the action in the dialog.
The job state changes to CANCELLED within a few seconds. The detail panel updates automatically.
Cancelling from the command line
You can also cancel from a terminal on the cluster:
scancel To cancel all your pending jobs at once:
scancel --user=$USER --state=PENDINGArray jobs
Cancelling an array job from the detail panel cancels the entire array — all pending and running tasks are stopped. To cancel a single task within an array, use scancel from the command line:
scancel _Note on COMPLETING jobs
Jobs in COMPLETING state are already finished and cannot be cancelled. Wait a few seconds for the state to transition to COMPLETED or FAILED.
Viewing Job Output and Error Files
PowerPortal lets you browse your home directory and view job output files directly in the browser — no need to SSH into the cluster.
Opening the output viewer
- Go to the Jobs page and click a job row to open the detail panel.
- Click View Output or View Error.
- The file contents are displayed in a scrollable panel, showing the last 500 lines.
The output and error buttons are only shown for your own jobs. If you open another user's job detail (staff view), the buttons are not available.
File browser
The Working Directory, Output file, and Error file fields on the Submit Job form each have a folder icon next to them. Click it to open a Select Path browser that lets you navigate your home directory (folders and files, with file sizes shown) and pick a path instead of typing one manually.
Default output file locations
If you did not set a custom output path in the submission form, Slurm writes output to:
slurm-<jobid>.outin the directory where the job was submitted from — typically your home directory. For array jobs the default is:
slurm-<jobid>_<taskid>.outFile not found?
- The job may not have started yet (PENDING) — output files are created when the job begins running.
- You may have set a custom output path that does not exist. Check the path in the job detail panel.
- The file may be on a path not accessible from the web server. Contact HPC support if this is the case.