Query exceeds the `statement_timeout` configured on the server or session. User or pipeline explicitly canceled the query. Connection was idle in transaction and hit `idle_in_transaction_session_timeout`. Long-running analytics query on an OLTP database with a short timeout

Step 1: Identify why the query was canceled from the error detail (timeout vs. user cancel).. Step 2: If it is a timeout, optimize the query or increase `statement_timeout` for long-running reports.. Step 3: Move heavy analytics queries to a read replica or a dedicated analytics database.. Step 4: Add indexes to speed up the query and reduce execution time.

Medium severitytimeout

Power BI Refresh Error:
57014

What does this error mean?

The query was canceled, either by the user, by `statement_timeout`, or by `idle_in_transaction_session_timeout`.

Common causes

1Query exceeds the `statement_timeout` configured on the server or session
2User or pipeline explicitly canceled the query
3Connection was idle in transaction and hit `idle_in_transaction_session_timeout`
4Long-running analytics query on an OLTP database with a short timeout

How to fix it

1Step 1: Identify why the query was canceled from the error detail (timeout vs. user cancel).
2Step 2: If it is a timeout, optimize the query or increase `statement_timeout` for long-running reports.
3Step 3: Move heavy analytics queries to a read replica or a dedicated analytics database.
4Step 4: Add indexes to speed up the query and reduce execution time.

Frequently asked questions

How do I prevent 57014 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