Webhooks: Temporary error connecting to Make.com … (error code: 520)

Features
1

I’ve recently implemented error logging into an app that sends Webhooks to Make and have noticed a lot of errors along the lines of “Temporary error connecting to Make.com … (error code: 520)”.

Have others ran into this same 502 error?

I know Webhooks have been unstable in the past but I thought that they were more stable now.

I’m considering adding something like Hookdeck in front of Make but want to be sure there’s nothing that can be done first.

1 Like
2

There is a partial outage today.

During an outage, incoming webhook requests will be lost (error 502) and it doesn’t even go into the webhook queue, because the server could not be reached.

For more information, see https://status.make.com/

samliew – request private consultation

Join the Make Fans Discord server to chat with other makers!

1 Like
3

Right but this has been happening almost everyday for 3 weeks - not just during reported outages.

1 Like
4

Perhaps outages should be reported more frequently then.

For technical issues like this, directly contacting support can often lead to a faster resolution. They have access to your specific account details, scenario and scenario logs, server-side logs, and internal tools and resources, which allows them to investigate more thoroughly than what we have access to.

You can open a new ticket here, or if you are unable to login for some reason, you can create another new free account to access the ticketing system (which is only available to logged-in users).

If you manage to get your issue resolved with support, we’d still love to hear about it! Sharing your solution on the forum can help others facing similar problems.

Join the Make Fans Discord server to chat with other makers!

1 Like
5

Just adding that I’ve also been getting a 520 error when making HTTP requests from one Make scenario to another Make scenario webhook consistently over the past few days.

But it looks like Make sometimes sends that error when the request content is too large (even though the app also has a dedicated error code for that issue). Reducing the size of the request content has resolved the issue.

1 Like