We have several flows that call other secondary flows using the http webhook step. These are flows that were created before the Subflow features was introduced. This has worked fine for months.
Starting yesterday, all of the secondary flows started returning 524, breaking the calling flow. Checking the secondary flow’s run log shows that it was successfully executed and returned a 200, yet the calling flow receives a 524.
Any thoughts? Lot of failing flows impacting our customers.
Hi @hanley
The webhook piece this documented, The webhook must respond within 30 seconds otherwise it will time out, Please use the subflow as it does not have this limitation.
Thanks for the response, but it’s also happening when it takes less than 30 seconds to respond. Here’s a more specific example:
Calling flow, today at 6:52am: Activepieces
The second step calls a secondary flow at Activepieces
That secondary flow shows a runtime of 3 seconds in its run logs. But the calling flow shows that step as taking 1 minute and 40 seconds with a 524 response.
Following up again. Still getting tons of 524s.
Any updates on this? Still getting 524s, and these are critical flows for our business. I understand switching to subflows would fix it, but we have so many interdependent flows like this that it’s just not feasible to do right now.
Now I’m encountering this issue on single flows called from outside ActivePieces. This is a different topic now so I’ll create a new topic.