Return Response

Dear ActivePieces Support Team,

I hope this message finds you well. I am reaching out to you due to an issue I’ve been experiencing while trying to configure the “Return Response” action in the response field. I have followed the provided instructions and am using the URL of my trigger followed by a /sync, as indicated. However, when making a request to this URL, I am unable to receive any response. Instead, all I get is a “time out” message.

I have double-checked my configuration multiple times to ensure everything is set up correctly, but the issue persists. I would greatly appreciate any guidance or solution you could offer for this matter.

I look forward to your feedback and suggestions.

Warm regards

1 Like

I was coming here to report this same problem. I created a very simple flow that should just return a static JSON:

When I try to go to the URL with “/sync” it times out. Here’s the URL of the webhook trigger:

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

Thanks!
Carl

1 Like

Yes, it’s exactly the same error. I must admit it’s a bit disappointing that such a simple yet crucial workflow doesn’t work in a tool that’s compared to Zapier or Make.

Seems to work for me:

Hi @cnasal - I’m not sure I’m getting your point but the link you posted returns Hello world already, here is a screenshot:

It’s good to know that any request to any URL on Activepieces will timeout within 30 seconds, this is because we use Cloudflare and we think it’s a good limitation to protect our infrastructure.

If you expect a slower flow to return a response, make sure you call it asynchronously instead, then send an HTTP request back to the requester to update the status.

I must admit it’s a bit disappointing that such a simple yet crucial workflow doesn’t work in a tool that’s compared to Zapier or Make.

@Mauricio_Perera I’m not sure if you’re a Zapier user, but Zapier doesn’t allow you to do this at all :wink:

1 Like

Hi,

I will document this limitation soon, but I also optimized our infrastructure today so it can be picked faster so can you please try again and let me know if that fixes your issue.

@abuaboud Thank you! That optimization solved my problem. It was taking too long to be picked up, and that’s why it was timing out. My real use case for this is working great now.

Thanks!
Carl

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.