Inspect and change resource limits

Use resource pools to investigate capacity or spending restrictions and, when authorized, change how many executions your workspace can run at once.

Before you start

Select the affected workspace, then open Administer → Resource pools. The cards shown depend on your access:

Card	Scope and access	What you can do here
Workspace concurrency	Selected workspace; governance.pool.view	Read limits, history and events. governance.pool.manage is also needed to edit or roll back.
Provider TPM	Organization of the selected workspace; governance.pool.view_org	Inspect provider/model token limits. This surface is read-only.
Daily cost	Organization of the selected workspace; governance.pool.view_org	Inspect the daily spending limit and available usage, history and enforcement events. This surface is read-only.

TPM means tokens per minute. Concurrency limits the number of simultaneous executions; it is different from a model’s token rate or the organization’s spending limit. Changing one does not remove the others.

Investigate a restriction

Open the relevant card and confirm its workspace or organization scope.
Review the configured limits, latest change reason and any override or circuit-break banner.
Check History and Events, where available, for the time and reason associated with the blocked work. An event feed is historical; it is not a list of every running request.
Compare the restriction with the failed run’s time and message. Follow Investigate a run for execution evidence.

An override temporarily changes a limit; a circuit-break can stop affected calls. Read the displayed scope, reason and expiry. Customer administrators cannot create or clear provider/cost overrides or circuit-breaks from these pages.

Insufficient history, a missing metric or a failed usage lookup does not establish zero activity. The concurrency page currently does not provide a completed impact projection; assess a proposed change with your platform operator rather than treating the placeholder as a capacity recommendation.

Change workspace concurrency

Reducing the limits can cause new work to wait or be refused. Increasing them can increase simultaneous resource use. Agree suitable values with the workload and platform owners before submitting.

Open Workspace concurrency, then select Edit caps.
In Edit concurrency caps, enter Soft cap, Hard cap and Lease TTL (seconds). The soft cap must be positive and no greater than the hard cap; the lease duration must be at least 30 seconds. The lease duration controls recovery of an unrenewed capacity reservation, not the maximum duration of every workflow.
Enter a meaningful Change reason explaining the intended effect.
Review the values and select Submit forward edit.
Check the active limits and recorded reason on the page. A successful edit creates a new configuration record; the previous record remains in history.

If No concurrency configuration is shown, the first successful edit creates the initial active configuration. Do not treat this state as proof of unlimited runtime capacity.

Restore a previous configuration

Open History and locate the prior configuration you intend to restore. Use Load more if necessary.
Select that row’s Rollback action.
In Roll back to a prior configuration, compare the current and target values and supply Change reason.
Select Confirm rollback, then check the active configuration and history.

Rollback creates another configuration record with the target values; it does not erase history. If you opened Rollback… without selecting a history row, close the dialog and choose the target from History first. If the current configuration changes during review, reload and reconfirm the comparison before proceeding.

If you cannot proceed

What happens	What to do
A card is missing or Restricted appears	Ask for the relevant workspace or organization read permission. Read access and edit access are separate.
History or events cannot load	Retry the lookup; do not assume that no earlier changes or enforcement events exist.
The submit control is disabled	Check required values, change reason, selected rollback target and management permission.
A change may have succeeded but confirmation was lost	Inspect the active configuration and history before submitting again.
Provider or cost limits need changing	Contact the platform operator with scope, workload, time window, observed restriction and requested business outcome. Never include secret values.

Technical resource-pool reference describes the contracts and platform-operator responsibilities.