Share feedback, ideas and get community help

Updated 4 months ago

Webhook Timeout

At a glance

The community member posted about an issue with a webhook, where they changed the timeout to 60 seconds but received an error 10 seconds into the process. Another community member suggested that the timeout is the duration the HTTP module waits for the server/endpoint response, and since it has already responded, there's no need to wait any longer. The original poster clarified that there was no response yet, and they are using an AI automation with GPT-4 which times out, while GPT-3.5 works. The community members discussed potential solutions, such as using the "response to webhook" on the end flow in Make, and the original poster was asked to try again in 10 minutes to see if a better error message is provided.

Hi sorry should have posted here. So I got a webhook and changed the timeout to 60 seconds but 10 seconds into the text I get this error
Attachments
CleanShot_2024-04-08_at_19.02.162x.png
CleanShot_2024-04-08_at_19.01.552x.png
m
K
B
8 comments
Hey @Kyle Behrend , the Timeout is the duration the HTTP module waits for your server/endpoint response. Since it has already responded, there's no need to wait any longer.

In this scenario, you should investigate why it's responding with error 500.
Thanks for the reply, but there wasn't a repsonse yet. I am sending it to Make and have a return module at the end. I'm using an AI automation. with GPT 4 it times out, 3.5 it works
GPT 4 it times out with 60s ?
not in make, it completes in about 30 seconds but by the time it completes Typebot already says it has timed out which it hasnt
Did you use response to webhook on the end flow on make ?
Hmm let me try that
I could not reproduce the issue but I just pushed something that should provide a better error message.
Can you try again in 10 min and let us know what the message is?
Add a reply
Sign up and join the conversation on Discord