Skip to main content

Set how many runners each subscription runs

Concurrent runners caps how many runners each of your subscription model accounts runs at once, counting runners still starting up. Raise it to get more tasks running on the subscriptions you have; lower it when a subscription keeps reaching its usage limit. One account can still have its own Max runners, which wins over this setting. API-key accounts have no cap unless one is set on the account.

Who can do this: the Org Owner or Org Admin role.

  1. In the sidebar, select Settings, then Tasks.

  2. Find Concurrent runners in the Quotas section. Beside the box, Default · and a number show the value used while your organization sets none.

    The Accounts category's Quotas section: Concurrent runners set to 4, with Default · 4

  3. Type the new number, from 1 to 64.

  4. Select Save at the top of the page, or Discard to put the old value back. Save counts the rows you changed, for example Save (1).

  5. Check the row: once your organization has its own value, Reset to … takes the place of the Default · line. Select it to go back to the default.

  6. In the sidebar, select Directory, then AI Accounts, and open each subscription you meant to follow this setting. Its Max runners should be blank, showing Org default and the new number. See Limit how a model account is used.

The cap is checked each time a run starts, so a lower number stops new runs on an account until it is back under the cap.