PalDock applies several limits at the same time so that no flow can run forever or block the system. Most of them you will never reach. This page lists them all in one place, so you know where to look when a run stops earlier than expected.
Timeouts you set yourself
Only two limits are yours to set, both on a node:
- HTTP request timeout, on an HTTP node. How long the node waits for the external server to answer.
- Webhook waiting time, on a Webhook node. How long the flow waits for an external system to call back.
Everything below is a system limit.
System timeouts
- Node: 5 minutes for one node from start to finish.
- Connection: 1 minute to evaluate an arrow and hand over to the next node.
- Scenario run: 250 minutes for the whole run, across all nodes and branches.
- Synchronous run: 50 seconds for a scenario that runs while someone is waiting for the answer.
- Webhook waiting inline: up to 40 seconds, when the node blocks the flow.
- Webhook waiting in the background: up to 48 hours, when the flow is released and resumed later.
- Webhook data: kept for 180 days after it arrives.
The synchronous limit is the one that matters in practice. Form validation, autocomplete and leads sent over the API all run while a visitor or an API caller waits, so the whole flow has to finish inside it, not just one node.
Size limits
- A scenario can have up to 50 nodes.
- A single node can run at most 30 times within one run. A loop without a Breaker ends here, with the run stopped and an error in the log, so give every loop a Breaker that ends it sooner and on your terms.
The limit of 30 is what protects you from a loop created by accident. If a node would run more often, the run is stopped and an error is written to the log. A Breaker node lets you set a lower limit yourself.
Retries
A node runs once. There is no automatic retry, and a failed node does not repeat on its own. If you need a second attempt, build it into the flow with a condition on the response.
What happens when a limit is reached
The run stops at that point and the reason is written to the run log. Branches that already finished keep their result. Nothing is retried silently.
Business limits
The limits above are technical. Volume limits, such as how many leads or clicks an offer may take per hour or per day, are configured separately. See Lead and Click Capping.
