Bit Flows Pro flow stops early (~20–21s) with fewer nodes than expected on WordPress (OpenLiteSpeed + lsphp). Where is the timeout coming from and how do I raise it?
Environment
- WordPress + Bricks Builder
- JetEngine (CCTs + Relations), JetFormBuilder (form + repeater)
- Bit Flows Pro (flows triggered by webhook)
- RunCloud server running OpenLiteSpeed with lsphp 8.1 (not PHP-FPM)
What the flow does
A JetFormBuilder form creates 4 CCTs of type “contatos” (x1), “atribuicoes” (x2) and “interacoes” (x1).
Then it sends a webhook to Bit Flows Pro with a repeater array so the flow can create N extra CCTs of type “interacoes“ and all the relations between them. The N extra CCTs and the connections they require are created with Rest API requests.
What I tried
Each repeater item equals a “cycle” of 6 nodes (create interacao, 5 relations).
With the 2 “intro” nodes at the start, a run with 2 items on the repeater should end with 14 nodes. A run with 3, with 20 nodes and so on.
If I have 3 items on the repeater, everything works fine, with the run ending with 20 nodes at around 19-20s. When I try to add a fourth item do the repeater, the run ends early with around 21 nodes, status SUCCESS, and duration ~19–21s.
The logs show no errors, both the Bit Flows Pro logs and the WP debug log.
What I suspect
A hard timeout based on the number of nodes or on ~20s (runner/job timeout) is aborting the flow before the final node(s), even though the flow UI shows “SUCCESS”.
