Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us for an expert-led overview of the tools and concepts you'll need to become a Certified Power BI Data Analyst and pass exam PL-300. 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.
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Power BI update to learn about new features.
User | Count |
---|---|
56 | |
54 | |
54 | |
37 | |
29 |
User | Count |
---|---|
78 | |
64 | |
45 | |
40 | |
40 |