This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
I have an Odata.connection that seems to timeout after 15 minutes therefore I have increased the timeout as suggested on several places. The result was the same so I tried lowering the timout to see if it had any effect. If I add a short timeout say 5 seconds I would expect a query to stop after this time has passed but it does not stop after 5 seconds. This seems to suggest increasing the timeout does not work either?
This is the row where I added the shorter duration:
Source = OData.Feed("https://<address>", null, [Implementation="2.0" ,Timeout=#duration(0, 0, 0, 5)]),
Solved! Go to Solution.
@Jonas_BIS , Have you given any time out at connection level?
Also, have you changed it in all queries?
We experience the same issue, like to know if there is already a solution. Ran the same test. Thanks!
Thank you for your reply. I do not know what you mean with connection level?
In the test I run one query to fetch a table and I would expect a low timeout setting to terminate my query after the timeout. But it doesn't stop in 5 seconds so I am
curious what the timeout setting actually does.
@Jonas_BIS , Have you given any time out at connection level?
Also, have you changed it in all queries?
Making sure it is set for all connections might actually do it. Have used another connection option now so will not test it but sounds like a reasonable solution.
Check out the April 2026 Power BI update to learn about new features.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 |
| User | Count |
|---|---|
| 5 | |
| 4 | |
| 4 | |
| 4 | |
| 3 |