Bug description
Every couple of days or so, the Superset application will start throwing the following error, which causes all of the dashboards utilizing snowflake to error out:
snowflake.connector.errors.OperationalError: 250003: 250003: Failed to get the response. Hanging?
It appears that this may be an underlying error in sqlalchemy rather than superset itself, but I thought I'd post it here since Superset doesn't appear to support any other drivers besides snowflake-sqlalchemy.
Note: For this implementation, superset is running as a containerized web application in AWS. To fix the issue, the task needs to be replaced, which re-establishes the connection, but is not a stable long-term solution.
Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist
- [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
- [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
- [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.
Comment From: dosubot[bot]
Hi @buehlerfa! I'm Dosu and I’m helping the superset team.
There aren't any existing Superset issues or discussions about the specific Snowflake error you're seeing. Superset manages Snowflake connections through SQLAlchemy and the snowflake-sqlalchemy dialect, with connection pooling and timeouts controlled via the database's Extra field (engine_params and connect_args). By default, Superset uses SQLAlchemy's NullPool, so connections are not pooled and are closed after use unless you override this behavior. Superset doesn't have built-in retry logic or self-healing for Snowflake-specific network failures—errors like "Failed to get the response. Hanging?" are surfaced as generic database errors, and mitigation relies on tuning pool and timeout settings in the connector's configuration or your infrastructure setup. You can find more on this in the Superset docs and Snowflake engine spec code.
For troubleshooting, enabling detailed logging in Superset (set LOG_LEVEL = logging.DEBUG in your config) can help you capture more diagnostic info if the issue persists. If you haven't already, you might also want to review your AWS/container networking and resource limits, as intermittent connectivity issues can sometimes be caused by infrastructure-level problems rather than application code. If the problem continues, consider tuning your connection and pool timeouts in the Extra field for your Snowflake database connection in Superset, and monitor for patterns in the failures to help isolate the root cause.
Let me know if you want more details on configuring these parameters or interpreting the logs.
To reply, just mention @dosu.
How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other 
Comment From: rusackas
Not sure if this is a bug, or an infra issue... I'll leave it open for others to weigh in on, but it might get moved to a "Help" Discussion if others aren't running into this.