Prioritize optimization model runs
Whether you’re submitting large batches of concurrent runs or need to manage a mix of production and staging runs, adding a priority ensures that your queue is ordered strategically and keeps operations running smoothly. Simply choose between 1 (highest) and 9 (lowest) to rank the run’s priority via the UI, API, or CLI. There are two ways to set it: at runtime or at the instance level.
Configure a priority at runtime. You may want to set priority at the run level to give shorter runs precedence, so long runs don’t block the queue. Below, we’ve set a run with a queue priority of 6.
Configure queue priority at runtime in the Nextmv UI
Configure a priority per instance. You may want to set priority at the instance level so all of your production runs take precedence over any staging or experimentation runs. Below, we’ve configured the queue priority on our staging instance.
Configure run queue priority on the instance level in the Nextmv UI
View and manage run queues
Once you’ve submitted your runs, you can view them all in the Nextmv UI. Use this dashboard to spotcheck priority, view the status of each run, and click into run details to see configuration, input, and more. Below, we can see runs in the queue ranked by priority along with their status, create date, and other metadata.
Review the run queue in the Nextmv UI