Type | Description | Actions / Implications |
---|---|---|
Pending | The initial status when a run is created; waiting for the node to be ready. | No actions performed; awaiting resource allocation. |
Initializing | The run is preparing to start; involves pulling container images and setting up import volumes of code, dataset, or model. | Resources are being consumed for preparation; credit is charged. |
Running | The run is actively executing the specified start commands in the specified working directories. | The main execution phase; credit is charged. |
Stopping | The run is finalizing; involves uploading data in the export volumes and completing final tasks before concluding. | Transition phase before completion; awaiting to be killed. |
Completed | The run has finished successfully, having executed all commands and finalized all tasks. | Final status indicating success; no further action required. |
Failed | The run has encountered an error and did not complete successfully. | Check the logs tab for error details; indicates a need for troubleshooting. |
Idle | The run is paused after execution due to enabled termination protection. | No active execution; credit is charged. |
Terminated | The run was forcefully stopped by the user at any point, except when in final statuses (Completed or Failed ). | Final status indicating user intervention; occurs if the user forces termination of the run. |
vessl.progress
. VESSL will calculate the remaining running time, which you can view by hovering over the status mark.Terminal
, you can SSH access the container through a web terminal. You can directly attach the SSH terminal to a run process or open a new shell.
Logs
tab. You can take various commands such as interrupting the process.