When using the Dataflow Query Execution REST API
Query Execution - Execute Query - REST API (Dataflow) | Microsoft Learn
queries are terminated after ~90 seconds.
This fixed timeout significantly limits real‑world usage. Only very small or simplified queries can be executed, while more complex or parameterized queries (although valid and supported in normal Dataflow refreshes) are cancelled.
This limitation makes it difficult to:
- Build generic or reusable Dataflow solutions
- Execute dynamic or complex queries via automation
- Use the API consistently compared to pipelines
Suggested improvements:
- Increase the default timeout
- Make the timeout configurable
Many users aim to build generic, reusable, and automated Dataflow solutions in Fabric.
The current timeout makes this difficult and forces unnecessary workarounds, such as:
- Over‑splitting queries
- Avoiding the API altogether
- Falling back to less flexible execution methods
Improving this would unlock significantly more value from the Dataflow Query Execution API.
1 Comment
- Oh yes, we need this
Recent ideas
Allow report creators to download their Own PBIX even when Downloads are restricted at tenant level.
In the current Power BI permission model, PBIX downloads are controlled exclusively through tenant‑level export settings and workspace roles. This creates a significant limitation for multi‑agency or...
