Skip to main content
A task is the stable behavior your application asks for. It owns a W&B project, datasets, fine-tunes, evaluations, analytics, Automation, and one or more routing versions.

Task alias

The alias is the model string used by your application, such as ticket-classifier. It is unique within a W&B entity and remains stable as models change. The bare alias always means version 1:
Pin a later version explicitly:

When to create a version

Create a new version when you need to experiment with a different model mix or provider parameters without touching the application’s current traffic. Each version has an independent routing configuration.
Creating a version does not move traffic. A caller reaches it only after changing model to alias@vN.

What versions do not copy

A version is not a copy of the task. Datasets, fine-tunes, evaluations, and Automation remain task-level resources. Dataset queries and Automation can select which task version’s traffic to use, and rollout can select which version receives a winner.
  1. Keep production on the bare alias and version 1.
  2. Create a new version with the proposed routing.
  3. Send internal or canary traffic to alias@vN.
  4. Inspect analytics and evaluations.
  5. Change the application’s configured model only when the new version is ready.
This creates the next version with its own routing. The response contains the assigned version number.
See Create a task version for the complete operation.
Last modified on August 25, 2026