Train your first model
Choose a dataset, base model, and training configuration in the UI.
Supported base models
For available models and selection guidance, see Supported training models. The UI can display the base model for an existing fine-tune even when the model is no longer available for new training runs.Create a fine-tune
Choose the following:- A ready dataset with training rows.
- Original outputs or a completed relabel run.
- A base model.
- An optional fine-tune name.
- Optional training parameters.
Training parameters
Open the advanced configuration only when you need control over:
With a scalar peak learning rate, Model Distillation creates the same schedule used by the ART SFT helper: 10% linear warmup followed by linear decay to zero. Supplying a full list preserves it exactly.
Status and artifacts
Fine-tunes move through Queued, Training, Deployed, or Failed. Training progress is reported from 0 to 100%. A deployed model includes an exact W&B artifact reference and is immediately selectable throughwandb-inference for evaluations and routing.
A failed fine-tune shows one of two actions next to its status, Retry or Create new model, depending on where the failure happened.
If the failure happened in the Model Distillation pipeline itself, such as during preparation, while monitoring the training job, or while recording the result, select Retry. What the retry does depends on how far the fine-tune progressed before the failure:
- If no training model was created yet, the retry restarts preparation.
- If a confirmed training job exists, the retry resumes it with fresh credentials, keeps the completed epochs, and trains only the remaining ones.
- If a training model exists but no confirmed submission can be recovered, the retry returns
409 Conflict, so create a new fine-tune instead.
training_failure_type to RemoteTrainingFailed, and a retry returns 409 Conflict with type remote_training_failed. A retry also returns 409 Conflict in any of the following cases:
- The fine-tune isn’t in the failed state.
- A retry that restarts preparation detects that the dataset changed after you created the fine-tune.
- A training model exists but no confirmed submission can be recovered.
Delete a fine-tune
Deleting a fine-tune removes the training model, its W&B artifacts, its generated outputs, and the UI record. A training model shared by several fine-tunes is removed when you delete its last owning fine-tune. Model Distillation removes the fine-tune from evaluation comparison sets and deletes evaluations that use it as ground truth. For a head-to-head evaluation that uses it as the primary participant, Model Distillation promotes the oldest remaining participant and marks the evaluation stale. An active evaluation blocks deletion. To delete a fine-tune in the UI:- Open the fine-tune’s page.
- Under Danger Zone, select Delete Fine Tune.
- In the dialog, review the affected evaluations and type the model name to confirm.
- Select Delete.
API: Delete a fine-tune (DELETE /tasks/{alias}/finetunes/{finetuneId})
API: Delete a fine-tune (DELETE /tasks/{alias}/finetunes/{finetuneId})
Deletion takes one request, and the server determines the affected evaluations and blockers itself:The request returns
202 Accepted with the deletion operation and its status. If you repeat the request while the operation is queued, running, or completed, the request returns the same operation. A repeated request also retries failed cleanup within the scope that the original request recorded. When the fine-tune is already gone and no operation exists, the request returns 204 No Content, and GET on the fine-tune returns 404 Not Found.To preview the affected evaluations and blockers before you delete a fine-tune, call GET /tasks/{alias}/finetunes/{finetuneId}/deletion-plan. The preview is informational and also reports the status of a running deletion. See Delete a fine-tune and Preview fine-tune deletion.API: List training jobs and artifacts (GET /tasks/{alias}/finetunes)
API: List training jobs and artifacts (GET /tasks/{alias}/finetunes)
To check progress, terminal status, and the artifact reference used in evaluations and routing, use this request:To start a job, use the request in Fine-tuning Quick Start. For this operation, see List fine-tunes.