Ensure that you, or someone on your team, has already configured a launch queue. For more information, see the Set up Launch page.
Add jobs to your queue
Add jobs to your queue interactively with the W&B App or programmatically with the W&B CLI.- W&B app
- W&B CLI
Add a job to your queue programmatically with the W&B App.


You can copy and paste values from other W&B runs that used your launch job by clicking on the Paste from… button.
7. From the Queue dropdown, select the name of the launch queue you want to add your launch job to.
8. Use the Job Priority dropdown to specify the priority of your launch job. A launch job’s priority is set to “Medium” if the launch queue does not support prioritization.
9. (Optional) Follow this step only if a queue config template was created by your team admin
Within the Queue Configurations field, provide values for configuration options that were created by the admin of your team.
For example, in the following example, the team admin configured AWS instance types that can be used by the team. In this case, team members can pick either the
- Navigate to your W&B Project Page.
- Select the Jobs icon on the left panel:

- The Jobs page displays a list of W&B launch jobs that were created from previously executed W&B runs.

- Select the Launch button next to the name of the Job name. A modal will appear on the right side of the page.
- From the Job version dropdown, select the version of the launch job you want to use. Launch jobs are versioned like any other W&B Artifact. Different versions of the same launch job will be created if you make modifications to the software dependencies or source code used to run the job.
- Within the Overrides section, provide new values for any inputs that are configured for your launch job. Common overrides include a new entrypoint command, arguments, or values in the
wandb.Run.config
of your new W&B run.

Within the Queue Configurations field, provide values for configuration options that were created by the admin of your team.
For example, in the following example, the team admin configured AWS instance types that can be used by the team. In this case, team members can pick either the
ml.m4.xlarge
or ml.p3.xlarge
compute instance type to train their model.
- Select the Destination project, where the resulting run will appear. This project needs to belong to the same entity as the queue.
- Select the Launch now button.