Get Job Status
Get detailed execution status for a customization job, including step-by-step progress and real-time training metrics.
This endpoint provides granular execution details including:
- Step-level status:
model-and-dataset-download→training→model-upload→model-entity-creation - Training progress:
step,epoch,max_steps,num_epochs,percentage_done - Latest metric values: one field per metric, named
<phase>_<metric>—train_loss,train_lr,train_grad_norm,val_loss, and whatever else your backend reports - Metric history:
metrics, holding each metric as a series of{step, epoch, value}points - Progress tracking:
downloaded_files,uploaded_bytes,progress_pct
Which metrics appear depends on the backend and the algorithm. See Checking Your Customization Job Metrics for how the names are formed.
To list jobs or get job definitions (model entity, hyperparameters, spec), use List Active Jobs instead.
Prerequisites
Before you can get the status of a customization job, make sure that you have:
- Configured a CLI context that points at your NeMo Helix deployment. Refer to Connect with CLI Contexts.
To Get the Status of a Customization Job
A submitted customization job runs on the platform’s Jobs service, so you poll its status through that service using the job name returned at submission (for example, automodel-a1b2c3d4e5f6). This works the same way for both the automodel and unsloth backends.
Use the SDK to get detailed job status:
These examples use the default workspace. If your current CLI context uses a different workspace, run nemo config set --workspace default first. To check, run nemo config view.
CLI
REST API
This example uses NHX_BASE_URL when it is set and falls back to http://localhost:8080. If your CLI context points at a remote deployment, export its URL first, and add an Authorization: Bearer $(nemo auth token) header for authenticated deployments. Refer to When to use NHX_BASE_URL.
Example Response
Active Job (Training in Progress)
Completed Job (All Steps Finished)