Request Failed Message when the Tool is actually s...
# support
z
Hi all, For some reason, all the tools that I create - that are only sending a Webhook to Make - all keep using the Request Failed Message even tho I can see the webhook is successfully received in Make and the 200 response is there. Any idea why?? Org ID 9b972444-4e74-4a5b-a4b1-36607c826c6f Call ID da1e5e9c-bb81-4d6f-a2c5-563878df606a Assistant ID 6249793f-4c8d-480f-84dc-12d7362111fe https://cdn.discordapp.com/attachments/1316814329529503744/1316814329965973546/Capture_decran_2024-12-12_180904.png?ex=675c6a69&is=675b18e9&hm=51d9933571b6306ef406d78ac4e869a2eddbdc80a5fbe3abf12afda6fa3ae958&
v
message has been deleted
@zako Hello! It sounds like you're experiencing an issue where your tools are reporting a failure despite Make successfully receiving the webhook and responding with a 200 status code. This could be due to a few different reasons, such as a misconfiguration in the way your tool is interpreting the response, a delay in the response that exceeds a timeout threshold, or an issue with the webhook setup itself. To help you troubleshoot this issue, I would recommend the following steps: 1. Double-check the configuration of your tool to ensure it's correctly set up to interpret a 200 status code as a success. 2. Verify that there are no delays in the response from Make that might cause a timeout. 3. Review the webhook setup in Make to confirm that it's correctly configured to send the 200 response back to your tool. 4. Check any logs or error messages that might provide more insight into why the tool is reporting a failure. If you've already checked these aspects and the issue persists, it may be helpful to reach out to the support team with the details you've provided, including the Org ID, Call ID, and Assistant ID, so they can investigate further. Would you like me to assist you with anything else at this moment?
You can continue this conversation by mentioning me in the message.
s
@zako sorry the late response, checking if your still struggling with the issue.
Because of no response closing this ticket.