Section 9 of 9
Quick reference
The numbers, field types, and rules you will look up while building — plus a calculator that tells you which limit you will hit first.
In plain terms
Enter how big your build will be and the calculator shows which limit you reach first and which package you need. The tables below hold everything else worth having to hand. Check Adobe’s documentation before relying on any of it.
Which limit will you hit first?
Result
First limit you hit: Records per workspace (Select) — 80% of 25,000 (near).
Package you need: Select — nothing in your numbers needs a larger package.
| Limit | Yours | Ceiling | Status |
|---|---|---|---|
| Records per record type | 8,000 | 25,000 | OK · 32% |
| Record types per workspace | 6 | 100 | OK · 6% |
| Fields per record type | 40 | 500 | OK · 8% |
| Formula fields per record type | 6 | 20 | OK · 30% |
| Connection fields per record type | 8 | 30 | OK · 27% |
| API requests per minute | 60 | 200 | OK · 30% |
| Records per workspace (Select) | 20,000 | 25,000 | Near · 80% |
Published limits change. These figures are Adobe’s published limits at the time of writing, and package names differ between Planning bundled with Workfront and Planning sold standalone. Confirm before you design around one.
Limits
| What | Limit | Notes |
|---|---|---|
| Sections per workspace | 50 | |
| Record types per workspace | 100 | Including record types created from templates. |
| Records per record type | 25,000 | No package raises it. |
| Records per workspace | Select 25,000 · Prime 500,000 · Ultimate 1,000,000 | |
| Records per instance | Select 500,000 · Prime 2,000,000 · Ultimate unlimited | |
| Fields per record type | 500 | |
| Formula fields per record type | 20 | 50,000 characters per expression. |
| Paragraph fields per record type | 20 | 10,000 characters each. Single-line text holds 1,000. |
| Connection fields per record type | 30 | |
| Records connected to one record | 500 | In a multi-select connection outside a hierarchy. |
| Parent records per child, in a hierarchy | 10 | |
| Record types per hierarchy / hierarchies per workspace | 4 / 5 | |
| Views per record type per user | 100 | |
| Automation conditions | 5 values | Referenced values across all conditions in one rule. |
| Sharing one Planning object | 100 entities | Users, roles, teams, companies, and groups. Bulk-share at most 100 records at once. |
| Import file size | 1 MB in the interface, 1.5 MB by API | To create a record type from CSV or Excel: 5 MB, 25,000 rows, 500 columns. |
| API rate | 200 requests per minute | A 429 response means you crossed it. |
Package gates
| Feature | Needs |
|---|---|
| Connections across workspaces | Planning Prime or Ultimate |
| Global record types | Planning Plus, or Prime or Ultimate alongside Workflow |
| Connections to AEM assets and folders | An AEM license |
| Connections to GenStudio brands | A GenStudio for Performance Marketing license |
| Fusion | Bundled at Workflow Ultimate or the Automation and Integration bundle; otherwise an add-on |
| Seeing Planning at all | A Workflow and a Planning license type; Light and Contributor users also need a layout template that exposes Planning |
Field types
New record types start with Name, Description, Start Date, End Date, and Status. The field types:
| Type | Notes |
|---|---|
| Single-line text | Up to 1,000 characters. Also Adobe’s recommendation for URLs — there is no URL type. |
| Paragraph | Up to 10,000 characters; at most 20 per record type. |
| Single-select, multi-select | Locked lists. Name and color values deliberately; the colors carry timeline views. |
| Date | Two are needed for timeline and calendar views. |
| Number, percentage, currency | |
| Checkbox | |
| Formula | Planning’s own syntax; at most 20 per record type and 50,000 characters each. |
| People | |
| Created by, created date, last modified by, last modified date | Automatic. Created by and last modified by cannot be pulled across as lookups. |
| Approved by, approved date | A cheap audit trail on a record; not a review process. |
| Record ID | |
| Connection, lookup | Created through the connection flow, not the field picker. |
There is no file or attachment field. Assets attach through connected AEM assets and folders or live on the connected Workfront project.
Rules worth remembering
- Record type or field: a record type if it connects to more than one other record type or carries details others look up; a field if it only ever describes one record type; a view if it is a way of looking at records.
- Connections: to record types in the same workspace on any package; to a Workfront Project, Program, Portfolio, Company, or Group; to AEM and GenStudio with their licenses. Cardinality is many-to-many, one-to-many, many-to-one, or one-to-one — and the last two move records when re-connected, without asking when done by API.
- Lookups: Created by, Last modified by, and Workfront typeahead fields such as Project Owner and Project Sponsor cannot be lookups.
- Views: timeline and calendar need two date fields and silently skip records with a missing or inverted pair. Deleting a field from a table view deletes it everywhere.
- Automations: created objects connect back to the triggering record; running again adds rather than replaces. The person running it needs create access in Workfront and Manage permission on the record.
- Permissions: four separate grants — workspace, record type, record, and view.
- Permanent decisions: a record type cannot move between workspaces, and some field types cannot change once records exist.
API basics
| Base | https://{customer-domain}/maestro/api/v2/… — version 1 shipped July 2024, version 2 May 2026. Name the version. |
|---|---|
| Authentication | OAuth 2.0 only, server-to-server or user-delegated. No /login, session IDs, or API keys. |
| Filters | Structured JSON: an AND or OR operator over conditions, each with a field ID, a condition such as HAS_ANY_OF, and values. |
| User IDs | People filters read a bare string as an Adobe IMS ID. For a Workfront ID, pass idType: “WF”. |
| Status codes | 409: another write won — retry with the current version. 429: rate limit. Version 1 returns 200 for every success; version 2 uses conventional codes. |
| Workflow API | /attask/api — projects, tasks, issues, templates, documents, approvals. |
| MCP | Adobe’s Workfront MCP server, plus Workfront and AEM MCP modules in Fusion. Runs under the user’s own permissions once an administrator enables it. |
Sources
- Adobe Workfront Planning documentation — terminology, request forms, automations, object limitations: Experience League article index
- Planning API reference, versions 1 and 2: developer.adobe.com/wf-planning
- Package contents and entitlements: Adobe Workfront product description