Skip to content

Queuing (prioritization)

Learn how to manage queuing when running with your tool of choice.

  • CLI: the Nextmv Command Line Interface (CLI).
  • Python SDK: a Software Development Kit (SDK) for Python developers.
  • Cloud API: an HTTP API for developers to integrate with the Nextmv platform.

Queuing lets you submit runs beyond your allowed maximum concurrency limits. Queues are maintained for each execution class and ordered by priority then age. The next run started upon a completion will be the highest priority, oldest request for the execution class of the completed run.

The run's priority can be a number between 1 and 9:

  • 1: is the highest priority.
  • 6: is the default priority.
  • 9: is the lowest priority.

Since queuing is specific to execution classes, run requests in execution classes that are not at limit will start without delay.

Queuing can be disabled altogether, in cases where you do not want a run request to queue. An example could be a real-time workload that must complete in a short time. In that case, when you submit the run and specify no queuing behavior, you'll receive a busy failure if you are at capacity and you can then handle it immediately.

Info

By default runs are queued if capacity does not exist. Queued runs have a default priority of 6. Disable queuing if you prefer to receive a busy error (429) if no capacity remains for the execution class.