Whenever an action fails, if the request has made it through to our backend systems it returns an HTTP status code 400 with an accompanying error message. Sometimes, these message can be a bit vague and it’s not clear what caused the problem. Check your platform logs to see if any additional information is provided there or, if possible, run the app or flow in debug mode for more granular error details (some platforms provide this option but some do not).
If you receive a specific error code other than 400, such as 401, 404, 503, or similar, then the response is coming from the various infrastructure layers between your application and our backend systems. This may include firewalls, load balancers, gateways, and other components, either within or without our hosting environment (many platforms have their own infrastructure for handling external connections). These issues can often be difficult to troubleshoot if you don’t have a development or network infrastructure background. Such errors are often transitory or intermittent, further complicating the issue. We can’t promise to solve every such incident, especially if the root cause is outside of the systems we control, but we will gladly help you troubleshoot. Just open and support ticket from our Help page, give us as much detail about the error as you can, and we’ll do our best to help track down the problem.