Connection was idle too long and closed by the server (`idle_in_transaction_session_timeout`). Connection pool returned a stale connection after a server restart. Application held a connection open across a long-running process

Step 1: Enable connection pool validation — configure `pool_pre_ping=True` in SQLAlchemy or equivalent.. Step 2: Reduce `idle_in_transaction_session_timeout` and ensure transactions are committed promptly.. Step 3: Retry the failed operation — a fresh connection should succeed.. Step 4: Review connection pool settings (`pool_recycle`) to recycle connections before server timeout.

High severityconnectivity

Power BI Refresh Error:
08003

What does this error mean?

The referenced connection handle no longer exists — it was closed or timed out before the operation completed.

Common causes

1Connection was idle too long and closed by the server (`idle_in_transaction_session_timeout`)
2Connection pool returned a stale connection after a server restart
3Application held a connection open across a long-running process

How to fix it

1Step 1: Enable connection pool validation — configure `pool_pre_ping=True` in SQLAlchemy or equivalent.
2Step 2: Reduce `idle_in_transaction_session_timeout` and ensure transactions are committed promptly.
3Step 3: Retry the failed operation — a fresh connection should succeed.
4Step 4: Review connection pool settings (`pool_recycle`) to recycle connections before server timeout.

Frequently asked questions

How do I prevent 08003 errors in automated pipelines?

Add retry logic with exponential backoff, validate data quality before loading, and monitor pipeline failures in MetricSign to catch this error early.

Official documentation: https://www.postgresql.org/docs/current/errcodes-appendix.html