Rate limits

Rate limits control how many agent interactions can run at the same time. They don’t limit how many you can run per day, only how many can be active simultaneously.

Quick reference

	Agents
Pro	25 concurrent interactions
Enterprise	100 concurrent interactions (customizable)
When limit is hit	Queued (Enterprise) or rejected
Scope	Organization-wide

Once an agent interaction finishes, it frees up a slot for the next one.

How rate limits work

Every time an agent interaction starts, the system checks whether your organization has an available slot. If it does, the execution starts immediately. If all slots are in use, the request is either queued or rejected depending on your plan.

Request arrives

An agent interaction starts, whether from the UI, API, Slack, Teams, or a scheduled trigger.

Slot check

The system checks how many executions are currently running across your organization against your concurrency limit.

Outcome

Under limit: execution starts immediately
At limit + Enterprise plan: request is queued and starts automatically when a slot opens
At limit + Pro: request is rejected

Agent rate limits

Agent rate limits control how many agent interactions can run at the same time across your organization.

Limits by plan

Plan	Concurrent Agent Interactions
Pro	25
Enterprise	100 (default, customizable per org)

What counts toward the limit

Counts

Any agent interaction that is currently running (actively processing a request or executing tools)
Interactions from all channels: web UI, Slack, Teams, API, and triggers

Does NOT count

Interactions that have finished (completed or failed)
Interactions that are queued (waiting for a slot)
Interactions that are idle (conversation open but agent is not actively working)
The Custom Operator Builder AI assistant
The App Policy builder assistant

Builder assistants (Custom Operator Builder, App Policy Builder) are excluded from agent rate limits so that building is never blocked by agent concurrency.

How the limit is determined

The system determines your organization’s limit in this order:

Custom organization limit: A custom agent concurrency limit on the org, if set.
Plan default: Falls back to the plan-based default shown above.
Per-user cap (optional): An optional cap on a custom role that restricts how many interactions a single user can run. When a user is in multiple custom roles, the most generous cap across their roles applies.

Example: Per-user caps within an organization

Setup:

Organization concurrency limit: 100
A user group has a per-user cap of 10

Result:

The organization can have up to 100 interactions at once across all members
Any user in that group can have at most 10 of those 100 running at once
Both limits must be satisfied for a new interaction to start

This lets admins prevent a single user from consuming the entire org’s capacity.

Automatic slot cleanup

If an agent interaction crashes or stops without finishing properly, Gumloop automatically frees its slot after approximately 4 hours. This means you never get permanently stuck at your limit because of a stuck interaction. Under normal circumstances, a slot frees up immediately when its interaction finishes. The 4-hour cleanup is only a safety net.

What happens when you’re rate limited

How the system communicates rate limiting depends on where the interaction comes from:

Web UI

When chatting with an agent in the browser:

Enterprise: The UI shows a “queued” indicator and waits up to 5 minutes for a slot to open. If a slot opens, the interaction starts automatically. If not, you are notified.
Pro: An error message is shown: “Too many concurrent agent interactions. Please try again shortly.”

API

When starting an agent via the API (Create session or Send message):

Enterprise: If you hit the limit, Gumloop queues the request. The response returns the session with a queued state and a queue_position so you can track progress.
Pro: The API returns HTTP 429 (Too Many Requests).

API response examples

Queued (Enterprise):

{
  "session": {
    "id": "sess_xYz789AbCd",
    "state": "queued"
  },
  "queue_position": 3
}

Rate Limited:

{
  "error": {
    "code": "gummie_rate_limit",
    "message": "Gummie rate limit.",
    "type": "rate_limit_error",
    "param": null,
    "details": {}
  }
}

Slack

When an agent receives a Slack message:

Enterprise: If queued, a message is posted in the thread: “Your agent interaction is queued (position #N). It will be processed shortly.”
Pro: An ephemeral message is sent: “You have too many agent interactions running at the moment. Please try again shortly.”

Microsoft Teams

Follows the same pattern as Slack: Enterprise users see a queued notification, others see an error message.

Scheduled & event-based triggers

Enterprise: At the limit, the triggered interaction waits in the queue and starts when capacity is available.
Pro: The trigger execution is skipped.

How the queue works

When an Enterprise organization hits the rate limit, requests are placed in a queue instead of being rejected.

When a running execution finishes and frees a slot, the next queued item starts automatically
The user who freed the slot gets slight priority: Gumloop checks their own queued items first, then the org-wide queue
Within each queue, items are processed in the order they were submitted (first in, first out)
If a queued item can’t start because of a per-user cap, it is moved to that user’s individual queue (not dropped)

Subagents

When your account’s concurrent-agent limit is full, new subagents wait and start automatically when a slot opens instead of failing. The cap of 10 concurrent subagents per task still applies. Stopping the parent task or reaching its deadline still ends queued subagents.

Webhook trigger request limit

Separately from concurrency, each webhook trigger accepts up to 100 requests per minute. The limit applies per trigger, regardless of sender or IP, and rejected requests count too. Requests over the limit get HTTP 429 (rate_limited) with a Retry-After header, and the agent does not run for them.

Tips for avoiding rate limits

Stagger your triggers

If you’re starting many agent interactions at once (for example, via webhooks), add small delays between them so they don’t all compete for slots at the same time.

Keep runs short

Shorter agent interactions free up slots faster. Give agents focused tasks to reduce their total execution time.

Upgrade your plan

If you consistently hit limits, consider upgrading. Enterprise plans have the highest limits and also unlock automatic queuing so requests are never lost.

Enterprise: Request a custom limit

Enterprise organizations can request custom concurrency limits that exceed the defaults. Contact your account manager or support@gumloop.com to adjust:

Agent concurrency: the org-wide limit on simultaneous agent interactions
Per-user caps via user groups: restrict individual users within the org

These are set at the organization level and apply to all members.

Summary

Aspect	Agents
What’s limited	Concurrent agent interactions
Limit scope	Organization-wide
Enterprise queuing	Yes (automatic)
Pro behavior	Rejected (error message or HTTP 429)
Stuck slot recovery	Automatic (~4 hours)
Customizable limits	Yes (Enterprise)
Per-user caps	Yes (via custom roles)

Credits

Learn about credit costs for agents

Custom roles

Configure custom roles and per-user limits

Get started

Core concepts

Enterprise features

Connectors

Quick reference

How rate limits work

Agent rate limits

Limits by plan

What counts toward the limit

Counts

Does NOT count

How the limit is determined

Automatic slot cleanup

What happens when you’re rate limited

Web UI

API

Slack

Microsoft Teams

Scheduled & event-based triggers

How the queue works

Subagents

Webhook trigger request limit

Tips for avoiding rate limits

Stagger your triggers

Keep runs short

Upgrade your plan

Summary

Credits

Custom roles

​Quick reference

​How rate limits work

​Agent rate limits

​Limits by plan

​What counts toward the limit

Counts

Does NOT count

​How the limit is determined

​Automatic slot cleanup

​What happens when you’re rate limited

​Web UI

​API

​Slack

​Microsoft Teams

​Scheduled & event-based triggers

​How the queue works

​Subagents

​Webhook trigger request limit

​Tips for avoiding rate limits

Stagger your triggers

Keep runs short

Upgrade your plan

​Summary

Credits

Custom roles

Quick reference

How rate limits work

Agent rate limits

Limits by plan

What counts toward the limit

How the limit is determined

Automatic slot cleanup

What happens when you’re rate limited

Web UI

API

Slack

Microsoft Teams

Scheduled & event-based triggers

How the queue works

Subagents

Webhook trigger request limit

Tips for avoiding rate limits

Summary