Skip to main content
Worker states represent the current operational status of your serverless worker instances. Understanding these states helps you monitor your workers’ health and manage your costs effectively.

Worker States in the Vast UI

The following table describes all available worker states that are shown to users in the UI:
State NameDescriptionBilling State
ReadyWorker is fully initialized with model loaded and ready to process tasksReady
LoadingWorker is loading resources or configurationsLoading
InactiveWorker is created but stopped, not currently processingInactive
DestroyingWorker is being destroyed and resources are being releasedNot billed
ErrorWorker has encountered an error and requires attentionNot billed
RebootingWorker is restarting to apply updates or recover from issuesBilled by previous state
CreatingWorker is being created and initializedCreating
StartingWorker is in the process of transitioning to Ready stateReady
StoppingWorker is in the process of transitioning to Inactive stateInactive
UpdatingWorker is in the process of being updated and rebootedReady
For more information on the specific breakdown of charges, please refer to Serverless pricing

Worker States in the Vast CLI and logs

The worker logs, accessible through the Vast CLI and UI, have more detailed descriptions of worker states to aid in debugging issues. These are described in the table below:
State NameDescriptionBilling State
Ready (IDLE)Worker is fully initialized with model loaded and ready to process tasksReady
Loading (LOADING)Worker is performing docker pull/run operationsLoading
Model Loading (MODEL_LOADING)Worker is loading the model for the first time in its lifetimeLoading
Inactive (STOPPED)Worker is created but stopped, not currently processingInactive
Destroying (DESTROYING)Worker is being destroyed and resources are being releasedNot Billed
Error (ERROR)Worker has encountered an error (version mismatch, error message, etc.)Not Billed
Rebooting (REBOOTING)Worker is restarting to apply updates or recover from issuesBilled by previous state
Creating (CREATING)Worker instance creation API call has succeededCreating
Created (CREATED)Worker is created but stopped in databaseCreating
Starting (STARTING)Worker is starting up after initial boot (not first time)Ready
Stopping (STOPPING)Worker is in the process of transitioning to stopped stateInactive
Pending (PENDING)Rental offer has been accepted, worker setup is pendingNot Billed
Update Ready (UPDATE_READY)Worker is prepared and ready for update rebootReady
Update Rebooting (UPDATE_REBOOTING)Worker is rebooting after update (non-alive)Ready
Update Starting (UPDATE_STARTING)Worker is starting up after update rebootReady