docs: Troubleshooting "Failed to run sql query: connection terminated due to connection timeout" (supabase#40336)

Author: thewheat

apps/docs/content/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.mdx

@@ -0,0 +1,25 @@
+---
+title = "Error: Failed to run sql query: Connection terminated due to connection timeout"
+topics = [ "database", "studio" ]
+
+[[errors]]
+http_status_code = 500
+message = "Error: Failed to run sql query: Connection terminated due to connection timeout"
+---
+
+![Failed to run sql query: Connection terminated due to connection timeout](/docs/img/troubleshooting/failed-to-run-sql-query-connection-terminated-due-to-connection-timeout.jpg)
+
+This error typically happens when the database is overloaded and causing an outage. As the database does not respond in a timely manner there can be a variety of symptoms such as tables not loading, error messages related to retrieving data and the dashboard seems to be unresponsive.
+
+- Check your database health in [Database reports](/dashboard/project/_/reports/database).
+- If needed, increase resources in [Compute and Disk](/dashboard/project/_/settings/compute-and-disk).
+
+Review the appropriate guides based on your scenario:
+
+- [High CPU usage](/docs/guides/troubleshooting/high-cpu-usage)
+- [High RAM usage](/docs/guides/troubleshooting/exhaust-ram)
+- [High Swap usage](/docs/guides/troubleshooting/exhaust-swap)
+- [High Disk I/O](/docs/guides/troubleshooting/exhaust-disk-io)
+- [Query optimization](/docs/guides/database/query-optimization)
+
+You can also set up alerts using a [Prometheus endpoint / Grafana charts](/docs/guides/telemetry/metrics) to monitor vital resources.