Forum Discussion
DataSource.Error: Web.Contents failed to get contents from app insights api endpoint
We are getting the following error, The query that is taking more time is
customEvents
| where name=='Audit:GetCareProviders' and timestamp >= startofday(datetime('2019-05-08')) and customDimensions.Result=='Success'
| summarize count() by NumberofCareProviders=todouble(customDimensions.CareProvidersAvailableInSearch), ServiceId=tostring(customDimensions.ServiceId),Date=substring(timestamp,0,10),client_Type
This query is used in power bi report this was working fine untill march 20th and we started to face this issue from march 21st. Any idea to response this is appreciated. This query seems to be getting timeout error.
The issue resolved on its own after few days. But still we didn't identified the root cause.
Few things suggested by power bi support team :
- Reduce the timeframe of the query in chunks
- Check whether you have the new Power bi version and save the report in another name and publish it into the workspace.
5 Replies
Ramji , New power bi version was released around the same time. Check any issue reported
Hi Ramji ,
I would suggest you test the API on Azure Developer portal to see if it works firstly: https://docs.microsoft.com/en-us/azure/machine-learning/studio/manage-web-service-endpoints-using-ap...
On Power BI side, I would suggest you update Power BI desktop to the latest version.
I have also found a similar post, please refer to it to see if it helps you.
DataSource.Error: Web.Contents failed to get contents from (400): Bad Request
If I have misunderstood your meaning, please provide a screenshot with the error or more details.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for your comment we will try out the APi test.
The issue is inconsistent and it automatically resolves down. The refresh automatically resolved yesterday. We again had this issue and after couple of retrial the data set is completed. We don't know about the root cause why the timeout fails we have the timeout specified in the report but need to look whether to increase the timeout option.
Hi Ramji ,
If you have resolved the issue, please mark the answer to close the case and help more people.
Best Regards
Community Support Team _ Polly
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
The issue resolved on its own after few days. But still we didn't identified the root cause.
Few things suggested by power bi support team :
- Reduce the timeframe of the query in chunks
- Check whether you have the new Power bi version and save the report in another name and publish it into the workspace.
