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

Next up in the FabCon + SQLCon recap series: The roadmap for Microsoft SQL and Maximizing Developer experiences in Fabric. All sessions are available on-demand after the live show. Register now

Reply
Echoy51
Frequent Visitor

Refreshing Issue

I have set 6 times daily refresh for my report, but I kept getting email like this:

Echoy51_0-1734308867075.png

Echoy51_1-1734308883719.png

This error frequency occurred 1-4 times a day...How to avoid this situation happening?

 

Many thanks,

 

Echo

 

1 ACCEPTED SOLUTION
v-hashadapu
Community Support
Community Support

Hi @Echoy51 ,Thank you for reaching out to Microsoft Fabric Community Forum.

Please consider reducing the refresh frequency. As:

1. Power BI has limits on how frequently data can be refreshed, especially if you're using an external data source (e.g., a web service) with Web.Contents calls. If you're hitting the data source too frequently (e.g., 6 refreshes daily), you might be triggering rate limits on the source's API, leading to a 429 status code.

2. Power BI itself has limits on the number of refresh operations that can be performed on a dataset within a given time period, especially for free and Pro licenses. If you refresh too often within a short span, this can lead to throttling.

3. If you're pulling data from an external API (via Web.Contents), the external service may have its own rate limits (e.g., only allowing a certain number of requests per minute or hour).

If this post helps, please mark it ‘Accept as Solution’, so others with similar queries may find it more easily.

View solution in original post

2 REPLIES 2
v-hashadapu
Community Support
Community Support

Hi @Echoy51 ,Thank you for reaching out to Microsoft Fabric Community Forum.

Please consider reducing the refresh frequency. As:

1. Power BI has limits on how frequently data can be refreshed, especially if you're using an external data source (e.g., a web service) with Web.Contents calls. If you're hitting the data source too frequently (e.g., 6 refreshes daily), you might be triggering rate limits on the source's API, leading to a 429 status code.

2. Power BI itself has limits on the number of refresh operations that can be performed on a dataset within a given time period, especially for free and Pro licenses. If you refresh too often within a short span, this can lead to throttling.

3. If you're pulling data from an external API (via Web.Contents), the external service may have its own rate limits (e.g., only allowing a certain number of requests per minute or hour).

If this post helps, please mark it ‘Accept as Solution’, so others with similar queries may find it more easily.

lbendlin
Super User
Super User

Run fewer requests if you want to avoid the 429.  group them better.

Helpful resources

Announcements
New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.

Power BI DataViz World Championships carousel

Power BI DataViz World Championships - June 2026

A new Power BI DataViz World Championship is coming this June! Don't miss out on submitting your entry.

Join our Fabric User Panel

Join our Fabric User Panel

Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.

March Power BI Update Carousel

Power BI Community Update - March 2026

Check out the March 2026 Power BI update to learn about new features.