Resource Groups

Control Work Queue Agent execution with lifecycle controls, concurrency, request circuit breakers, and time-window cost limits.

4 min read

A Resource Group is the execution boundary shared by the queues that select it. It controls whether agent work may run and how much work can run at once.

From the Work Queues list, select View Resource Groups.

The Resource Groups list with the fictional queue's default group paused

The list shows each group's description, last start time, snooze time, status, maximum concurrency, and timestamps. Select a group to edit it. Row selection enables Start Resource Group, Abort Resource Group, and Archive Resource Group where those actions are valid.

Queue-level resource status

Inside a queue, select the status chip beside the queue name.

The paused Resource Group Status modal with lifecycle controls and guardrail summary

Control	What it does
Start	Starts processing eligible work now.
Abort	Stops the active Resource Group job. Use it when running work must be interrupted.
Pause Auto Run	Prevents agent work from starting automatically.
Auto Run	Allows the group to start when eligible work is assigned to an agent.
Edit Resource Group	Opens the complete guardrail configuration.

The modal also shows the current job ID, maximum concurrency, circuit breaker, cost window, and description. Pausing the group does not change item statuses or delete assignments; it stops eligible agent work from starting.

Resource Group settings

The Resource Group editor with concurrency and cost-window settings

Identity and concurrency

Setting	What it does
Name	Labels the Resource Group in queue settings and resource controls.
Description	Explains which workloads share the group and why.
Max Concurrent Requests	Caps the number of requests the group can run at once, up to the product maximum shown in the UI.

Use a shared group when several queues should compete for the same budget and concurrency pool. Use separate groups when workloads need independent guardrails or lifecycle controls.

Request Circuit Breaker

The per-request circuit breaker protects one request:

Setting	What it does
Enable Request Timeout	Stops a request after the configured days, hours, minutes, and seconds.
Enable Cost Limit per Request	Stops a request when its tracked model cost reaches the configured amount and currency.
Maximum Cost per Request	Sets that request-level cost ceiling.

Request limits protect against one runaway execution. They do not replace the group's total time-window budget.

Cost Per Duration Limit

This guardrail limits aggregate tracked cost over a repeating window.

Setting	What it does
Duration Type	Uses minutes, calendar days, or calendar months.
Duration Value	Sets the number of selected units in one window.
Maximum Cost	Sets the total tracked cost allowed in the window.
Currency	Sets the reporting currency.
Original Start Date	Shows the automatically calculated anchor used for recurring windows.

The UI requires a Cost Per Duration Limit before saving a Resource Group. Choose a window that matches how the workload is reviewed. A short operational window can catch spikes; a calendar-day or month window can enforce a broader budget.

How eligible agent work is chosen

An item must be assigned to an agent, have an eligible action state, and belong to a queue using the Resource Group. Snoozed items remain ineligible until Snooze Until. The group then applies its status, concurrency, circuit breaker, and cost window before work can begin.

When an item never starts, check in this order:

The queue status chip is Auto Run or the group has been started.
The item is assigned to a registered agent.
The item is ready, not waiting, snoozed, or already running.
Snooze Until is empty or in the past.
The concurrency and cost limits still allow another request.
The agent Flow and required Connections are available.