You are here:
Blueprint Limits in Agentforce Operations
Blueprints have limits on the number of tasks, fields, and form items they can contain. These limits help you avoid the performance issues that come with oversized blueprints.
You are here:
Blueprints have limits on the number of tasks, fields, and form items they can contain. These limits help you avoid the performance issues that come with oversized blueprints.
| License Required |
|---|
This feature is a workspace that’s external to your Salesforce org and requires an Agentforce Operations license. To purchase an Agentforce Operations license, contact your Salesforce account executive. |
As you build a blueprint, Agentforce Operations checks it against a set of limits. If a blueprint exceeds a limit, a warning banner appears that identifies which limits were exceeded, on which tasks or forms, and by how much. Until the blueprint is back within all limits, you can't publish a draft blueprint or create workflows from it.
You can keep editing a blueprint that exceeds a limit. Only publishing and workflow creation are blocked. To see why an option is disabled, point to it.
To bring a blueprint back within its limits, reduce the number of tasks, fields, or form items that the banner identifies. If your blueprint is too large to fit within the limits, split it across linked blueprints. Linked child blueprints don't count toward the parent blueprint's limits. Each blueprint is evaluated independently, so you can use linked blueprints to break large blueprints into smaller components without hitting limits. For more information, see Build Complex Processes with Linked Blueprints in Agentforce Operations.
These limits apply to each blueprint.
| Limit | Value |
|---|---|
| Total tasks per blueprint | 150 |
| Automation tasks per blueprint | 50 |
| Total fields per blueprint | 1,000 |
| Items per form (including the intake form) | 500 |
For all entitlements and limits, see Entitlements and Limits for Agentforce Operations.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.