Flow limits
These limits affect the creation of flows.
Some connectors have additional limitations; see the connector documentation for your connectors to learn more.
For PingOne standard platform limits, see PingOne standard platform limits.
Flow limits
| Property | Limit | Description |
|---|---|---|
Resource |
100 |
Your environment can contain a maximum of 100 of each entity type. This limitation applies to flows, variables, and connections, but not to end users. Each flow is limited to 100 stored versions. |
API payload |
10 MB |
The maximum payload size for any API call (such as POST, GET, or DELETE) made within a flow. |
Number of nodes that can be run per flow invocation |
Twice the number of nodes in the flow or 70, whichever is higher |
Maximum number of nodes that can be run. This limit is distinct for each flow, so if a flow launches a subflow, both flows can run a number of nodes up to this limit. |
Flow timeout |
Default is 5 minutes. Maximum possible is 2 days. |
A timeout value for the entire flow, beginning when the flow is invoked. Editable for each flow. For more information, see Editing flow settings. |
Flow HTTP response timeout |
Default is 15 seconds. Maximum possible is 120 seconds. |
A timeout value for any HTTP call made by any node in the flow. Editable for each flow. For more information, see Editing flow settings. |
Node payload |
1 MB |
The maximum size of the payload sent by a node to future nodes. |