Flow run shows successful execution but returns timeout to caller

[hanley]

I have some flows that start with a webhook. Starting earlier this week, calling them ends in a time out, even though the flow’s logs show they were executed correctly.

To recreate the issue:

Call this webhook:

https://cloud.activepieces.com/api/v1/webhooks/kO8Fx9oPoXRnp2cAZLWjH/sync

with raw body:

{
    "emailAddress":"[email protected]"
}

If you check the run logs of that flow (Activepieces) it shows that it was executed in 1 second and returned a 404 (as it should). However the caller, in my case Postman, says it took longer than 30 seconds and timed out.

I posted a second topic related to this a couple days ago when I thought this was only happening when calling one flow from another flow. But that’s no longer the case.

Please fix this ASAP. These are critical flows that were working great up until Tuesday. Now we’re overloaded with AP errors resulting in customer issues.

[hanley]

Any thoughts? So many of our flows are doing this. It’s really impacting our infrastructure.

[hanley]

Can I please get a reponse/fix for this? It’s been going for almost a week now. It’s a real problem.

[hanley]

Swapping out the old HTTP return step for the newer Webhook return step fixed the issue. Thanks for the assistance [he shouted into the void].