Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!Learn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
Hi all,
I am working with a REST API that sends in POST. I am using the code below, and I am able to refresh in desktop client after about 20 minutes. However, when I perform schedule refresh I get the following error: "The underlying connection was closed: The connection was closed unexpectedly". It seems like the cloud client is "giving up too easily". I am using a datagateway.
let
Source = let
Source = let
url = "https://url.com",
body = "{""id"": ""XXX"" }",
Source = Json.Document(Web.Contents(url, [Timeout= #duration(0, 1, 0, 0),
Headers = [#"Authorization"="Basic XXXX", #"Content-Type"="application/json", #"Connection" = "keep-alive"],
Content = Text.ToBinary(body)
]))
The API has a lag before data is sent back for large queries. I am wondering if there is a way to keep the connection open in my mQuery code. I already tried adjusting the timeout with no luck.
I resolved this by pre-caching the query. It has something to do with the fact that if the cloud refresh isn't recieving a response, it will kill the connection after about 6 minutes (time out does not solve this). Meanwhile, if the query is preloaded, even if its large, cloud refresh works. I took a look at those sources, I didn't see anything applicable but I do appreicate your help. I'm leaving this open in case anyone ever solves it.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 61 | |
| 54 | |
| 40 | |
| 16 | |
| 14 |
| User | Count |
|---|---|
| 98 | |
| 84 | |
| 35 | |
| 30 | |
| 25 |