Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.

Reply
ZetaNaruto1729
New Member

Sometimes refresh feature doesn't work on powerbi website.

Hi!

I am using a custom query to fetch the data. Basically, query is downloading an export zip (export is first initiated by script)using a graphql API. And then query pre-processes the data.

In the script I am using two base URLs one is a graphql endpoint and one is a base url for export. Graphql enpoint is static in a query and export base URL is a parameter. Credentials for both the URLs are set as below:

creds_1 (1).pngcreds_2 (1).png

The refresh works perfectly fine on power bi desktop. But on power bi website, it works randomly (i.e. sometimes it works and sometimes it doesn't). When it works, refresh is finished within 1-2 mins. When it doesn't work, it takes several hours to even show an error message. I have observed following error messages:

1.png2.png

What can be the causes of this issue ? What should I do to solve this issue ?

Kindly Advise.

1 ACCEPTED SOLUTION
v-jayw-msft
Community Support
Community Support

Hi @ZetaNaruto1729 ,

 

The first error is timeout error.

Scheduled refresh for imported datasets timeout after two hours. This timeout is increased to five hours for datasets in Premium workspaces. If you encounter this limit, consider reducing the size or complexity of your dataset, or consider refactoring the large dataset into multiple smaller datasets.

The second error is a credentials error.

If you get a credentials message, it could mean:

  • The usernames and passwords that you used to sign in to data sources aren't up to date. In Power BI, go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source.

  • Mashups between a cloud source and an on-premises source, in a single query, fail to refresh in the gateway (personal mode) if one of the sources is using OAuth for authentication. An example of this issue is a mashup between CRM Online and a local SQL Server instance. The mashup fails because CRM Online requires OAuth.

    This error is a known issue, and it's being looked at. To work around the problem, have a separate query for the cloud source and the on-premises source. Then, use a merge or append query to combine them.

 

Best Regards,

Jay

Community Support Team _ Jay
If this post helps, then please consider Accept it as the solution
to help the other members find it.

View solution in original post

2 REPLIES 2
v-jayw-msft
Community Support
Community Support

Hi @ZetaNaruto1729 ,

 

The first error is timeout error.

Scheduled refresh for imported datasets timeout after two hours. This timeout is increased to five hours for datasets in Premium workspaces. If you encounter this limit, consider reducing the size or complexity of your dataset, or consider refactoring the large dataset into multiple smaller datasets.

The second error is a credentials error.

If you get a credentials message, it could mean:

  • The usernames and passwords that you used to sign in to data sources aren't up to date. In Power BI, go to refresh settings for the dataset. In Manage Data Sources, select Edit credentials to update the credentials for the data source.

  • Mashups between a cloud source and an on-premises source, in a single query, fail to refresh in the gateway (personal mode) if one of the sources is using OAuth for authentication. An example of this issue is a mashup between CRM Online and a local SQL Server instance. The mashup fails because CRM Online requires OAuth.

    This error is a known issue, and it's being looked at. To work around the problem, have a separate query for the cloud source and the on-premises source. Then, use a merge or append query to combine them.

 

Best Regards,

Jay

Community Support Team _ Jay
If this post helps, then please consider Accept it as the solution
to help the other members find it.

We have tried making these API calls using Postman and it responds back within a few seconds. It seems there is some other issue that leads to the timeout error.

 

Moreover, we have also verified that the credentials for the API calls are valid.

 

Could you help us with this issue?

Helpful resources

Announcements
RTI Forums Carousel3

New forum boards available in Real-Time Intelligence.

Ask questions in Eventhouse and KQL, Eventstream, and Reflex.

MayPowerBICarousel

Fabric Monthly Update - May 2024

Check out the May 2024 Fabric update to learn about new features.

LearnSurvey

Fabric certifications survey

Certification feedback opportunity for the community.

Top Solution Authors
Top Kudoed Authors