Read the run state
| State | Meaning | Next action |
|---|---|---|
| Draft / Ready | Configuration exists; no active solver is implied. | Review input and run when ready. |
| Queued | Waiting for a worker or a dependency. | Check the selected destination, its connection, and prerequisite jobs. |
| Running | The worker has claimed the job. | Inspect stage, log tail, and resource details; allow time for expensive stages. |
| Completed | The result was uploaded and accepted. | Inspect convergence and scientific validity, then open results. |
| Failed | Preparation, execution, or upload failed. | Read the reason and solver log before retrying. |
| Cancellation requested | A running job is being asked to stop. | Wait for the worker heartbeat and terminal status. |
| Cancelled | The run was stopped or removed from the queue. | Retain useful logs; start a new run if needed. |
What cores and RAM mean
Recorded cores are the allocated vCPUs or worker processes, and RAM is the configured memory limit. These are different from actual CPU utilization or installed physical memory.
Expand resource details in the execution log to inspect reported backend allocation, elapsed time, MPI processes, and QE memory or timing estimates when available. Missing historical data is shown as not reported.
A local worker is still constrained by service-side job limits. The current deployment limits appear in Account and the compute destination panel. Jobs requesting more than the server permits are rejected instead of silently resized.
Cancel intentionally
- A queued local job can be removed from the queue.
- A running cancellation reaches the worker through its heartbeat, so completion is not instantaneous.
- Closing the browser does not cancel a submitted calculation.
- Disconnecting a personal credential revokes access and may interrupt upload; use the calculation cancellation action before replacing a credential during an active run.