Has anyone received a 502 Bad Gateway response from calling a POST REST service via an integration and if so what was the cause and how did you fix the issue?
We have an integration that calls an internal service to send emails from a corporate email account that can include attached documents. It works fine with an attachment of around 1.5MB but returns a 502 Bad Gateway response with an attachment of around 2.5MB. The service itself is tested with attachments up to 10MB. When we get the 502 Bad Gateway response there is no record of the request ever reaching the service endpoint (it's not in the service logs).
The response body shown in Appian is:
Discussion posts and replies are publicly visible
AFAIK there is nothing you could do in Appian. If you tested the service itself, could it be that there is something in-between Appian and the service which you skip when testing directly? I think of a proxy, reverse-proxy or API management.
Yes that's where I think the issues is, somewhere in the connectivity between Appian and the service, so it could be the VPN, firewall, load balancer, etc. I'm just not sure how we trace that to identify where the bottleneck is.
The only way is to try to find out which hops are in-between and check logs&config on each.
Ok thanks for the response Stefan
© 2022 Appian. All rights reserved.