To maintain platform stability and performance for all users, we have established the following operational boundaries. Please consider these when designing your integration flows:
Limit Category | Value | Description |
Webhook Response Time | 30 Seconds | The time allowed for a flow to acknowledge an incoming webhook trigger. |
Maximum File Size (Files Utility) | 10 MB | The largest file size permitted for steps from the Utility (e.g., files helper). |
Flow Execution Timeout | 5 minutes | The maximum total time a single flow execution can run before it is automatically stopped. |
Memory Limit | 512 MB | The maximum amount of memory available for a single flow execution. |
Code time execution | 90 seconds | The maximum total time to keep running code in a step. |
Job retries | 24 hours | The data required to retry a failed execution is stored for 24 hours. You can manually retry any failed step within this window. After 24 hours, the execution data is cleared from memory, and retries will no longer be available for that specific run. |
Logs retention | 30 days | The maximum retention period for log data (runs) is 30 days. During this period, you will be able to analyze and view the details of each flow run. |
Concurrent executions | 50 | The total number of runs concurrent at the same time per org. |
Flows | Unlimited | The total allowed active flows. |
Steps in a flow | Unlimited | The maximum number of steps allowed within a single flow is subject to memory limitations and the complexity of the code. |
NPM packages | Not allowed | The use of NPM packages is prohibited in ST environments when a VPN is active. |