Skip to main content

Plans & Limits

Understand the limits that come with your Service Plan, where to track them, and what happens when you reach one.

Every Workspace runs on a Service Plan that defines how much it can use: how many workflow runs it can start, how much data it can store, how many people can join, and more. This page describes each limit and how the platform behaves at the boundary. The actual numbers for each plan are listed on the Pricing pagethey are not repeated here.

How it works​

Limits come in two kinds:

  • Usage allowances reset at the start of every billing period Sessions started and AI tokens consumed. A new period gives you a fresh allowance.
  • Capacity limits are running counts that do not reset Processes, collaborator seats, Environments per Process, storage, and Dynamic Modules. You free up capacity by removing what you no longer need.

The Dashboard shows a card for each metered resource with your current usage, the plan limit, and a progress bar. When usage on the Executions, Storage, or AI Tokens card passes 80% of its limit, an Upgrade shortcut appears on the card, taking you straight to Billing. When a limit stops a workflow, the error is recorded with a code in the Plan Limits (9xxx) range you can find it on the Logs page and in Session Details.

Session limits​

These limits protect your allowance and keep individual workflow runs within the bounds of your Service Plan. When one is reached mid-run, the Session stops with an error you can inspect in Session Details.

Sessions per billing period​

Each Session started in your Workspace counts toward your plan's execution allowance for the current billing period.

  • Where to track it the Executions card on the Dashboard shows your usage bar and, once a trend is available, a projection of when you would run out at the current pace.
  • When you reach it new Sessions no longer start, and the attempt fails with error 9001 ("Execution limit reached for your current plan"). Already-running Sessions are not affected. The allowance resets when the next billing period begins.

Simultaneous Sessions​

Your plan caps how many Sessions can run at the same time.

  • Where to track it the Running Now card on the Dashboard shows the live count and the peak reached this period against your plan's cap.
  • When you reach it a new Session cannot start until a running one finishes, and the attempt fails with error 9002. Retrying after running Sessions complete usually succeeds.

Tasks per Session​

A single Session may execute at most a plan-defined number of Task steps. This mainly catches unintended infinite loops in a Process.

  • Where to track it the Transactions card on the Dashboard shows the total Task steps executed this period; the per-Session count is visible in Session Details.
  • When you reach it the Session stops with error 9003. Review the Process for loops or unnecessarily long branches.

Session duration​

A Session may run for at most a plan-defined amount of time.

  • Where to track it the Running Now card highlights Sessions that are running much longer than usual; Session Details shows each Session's duration.
  • When you reach it the Session stops with error 9004. Review the Process for long waits or slow external calls.

Data size per Session​

The data a Session carries its variables, messages, and results may not exceed a plan-defined size.

  • Where to track it the Transactions card on the Dashboard shows the average amount of data a Session carries.
  • When you reach it the Session stops with error 9006. Reduce the amount of data your Tasks read into or keep in the Session.

Workspace capacity limits​

These limits apply to what exists in the Workspace rather than to a single run. Reaching one blocks the action that would exceed it nothing already created is affected.

Processes​

Your plan caps how many Processes the Workspace can contain.

  • Where to track it the Processes card on the Dashboard.
  • When you reach it creating another Process is blocked with a message that your plan's Process limit is reached. Delete Processes you no longer use, or upgrade.

Collaborator seats​

Your plan caps how many team members the Workspace can have. Only accepted members use a seat pending invitations do not count until they are accepted. See Collaboration.

  • Where to track it the Collaborators card on the Dashboard, or the Collaboration page.
  • When you reach it sending a new invitation is blocked with a message that your plan's collaborator limit is reached. Revoke access for members who no longer need it, or upgrade.

Environments per Process​

Each Process can have at most a plan-defined number of Environments.

  • Where to track it the Environment list of each Process.
  • When you reach it creating another Environment for that Process (including a deployment that would create one) is blocked with a message that your plan's Environment limit is reached. Other Processes are unaffected the limit is per Process.

Storage​

Files your workflows and team store in the Workspace count toward a total storage limit. Storage is cumulative it does not reset with the billing period.

  • Where to track it the Storage card on the Dashboard, and the Storage page for the individual files.
  • When you reach it Tasks that write files fail with error 9007, and reads keep working. Delete files you no longer need on the Storage page, or upgrade.

Dynamic Modules​

Your plan caps how many Dynamic Modules custom Modules that run in their own dedicated container the Workspace can have. On some plans the feature is not included at all.

  • Where to track it the Dynamic Modules card on the Dashboard.
  • When you reach it creating another Dynamic Module is blocked with a message that your plan's limit is reached (or that the feature requires an upgrade). See External Modules.

API request rate​

Programmatic access to your Workspace MCP connections and other API clients is limited to a plan-defined number of requests per minute. Normal use of the web app does not count against this limit.

  • Where to track it the per-minute limit for your plan is listed on the Pricing page.
  • When you reach it further API requests are rejected with a rate-limit response (error 9005) stating how many requests per minute your plan allows. The limit is measured over the most recent minute, so capacity returns as earlier requests age out clients should wait briefly and retry.

AI Assistant tokens​

The built-in AI Assistant consumes AI tokens from a per-period allowance defined by your plan. The counter resets when a new billing period begins.

  • Where to track it the AI Tokens card on the Dashboard (with a projection of when you would run out at the current pace), and the percentage badge in the AI Assistant panel's header.
  • When you reach it the AI Assistant stops answering and tells you the AI token limit is reached for this billing period. It resumes when the next period starts, or immediately after an upgrade.

Raising your limits​

Upgrading your Service Plan raises every limit at once, effective immediately. See Billing for the full subscription workflow.

  1. Navigate to Billing from the sidebar (visible to Workspace Owners and Admins), or click the Upgrade shortcut on a Dashboard card.
  2. Click Find a plan (or Change Plan if you already have a subscription).
  3. Compare the plans, switch between Monthly and Yearly pricing, and click Upgrade on the plan you want or Buy now when subscribing for the first time.
tip

The Dashboard's Executions and AI Tokens cards project the date you would exhaust the allowance at your current pace upgrade before that date to avoid interrupting your workflows or the AI Assistant.

Temporary verification issues​

On rare occasions the platform is temporarily unable to verify your Service Plan limits, and a Session start is refused with error 9008 even though you have allowance left. This is a platform issue, not your usage retry shortly, and contact support if it persists.

Best practices​

  1. Watch the projections the Executions and AI Tokens cards forecast when you will run out; act before the date, not after.
  2. Investigate 9003 and 9004 early a Session that hits the Task or duration limit usually contains a loop or an unbounded wait worth fixing regardless of plan size.
  3. Clean up storage periodically storage never resets, so remove files you no longer need on the Storage page before the limit blocks a workflow.
  4. Free seats you don't use revoke access for former collaborators so invitations for new ones are not blocked.
  5. Throttle API clients keep MCP and API integrations below your plan's requests-per-minute rate and honor rate-limit responses by waiting before retrying.
  • Dashboard usage cards, progress bars, and exhaustion forecasts.
  • Billing subscriptions, upgrades, and invoices.
  • Error Codes full reference for the Plan Limits (9xxx) range.
  • Collaboration how invitations and seats work.
  • MCP Access programmatic access subject to the API request rate.