"502 Bad Gateway error" when running queries

The 502 Bad Gateway error can be attributed to different things. The most common are:

1. Query queue overload
   There are too many queries in the query queue. Panoply support can help identify and clear them if applicable.
 
2. Executing a long-running query in the Workbench tool
   Using the Workbench tool in Panoply to execute a long-running query or those that potentially return large amounts of data will raise the error. The Workbench tool has a default timeout of two minutes, and queries that exceed beyond that will fail.
   
   For executing long-running queries, we recommend using external or third-party SQL client tools to connect to Panoply like:
   • SQL Workbench/J
   • DBeaver
   • DataGrip

If you're still getting slow performance from your queries, please contact support@panoply.io.