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

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Learn more

Reply
IanCockcroft
Post Patron
Post Patron

Disabling gateway refresh

Hi   guys, I have an issue.

Our data source moved servers and the gateway throws an error. We can only get it fixed after End-of-Year freeze in July.

I can refresh data in dev desktop and publish it until we can fix the gate.

The only problem is, when    opening the report in the web service,   it tries  to refresh automatically.  Breaking  some visuals.

Is it possible to disabe auto refresh or the gateway until we can get it fixed?

If  so, how?

thanks a mil   guys

Ian

1 ACCEPTED SOLUTION
lbendlin
Super User
Super User

"The only problem is, when    opening the report in the web service,   it tries  to refresh automatically.  Breaking  some visuals."

 

I don't think that is correct. An unsuccessful dataset refresh does not blit the data over.

 

The way the service works is :

- a dataset refresh request does not work on the dataset itself but on a shadow copy. 

- only if the refresh is successful it will swap the new dataset in and the old out (blitting)

 

So your failed gateway based refreshes are unfortunate for the service performance (wasting resources) but they have no impact on the existing dataset.

View solution in original post

4 REPLIES 4
V-lianl-msft
Community Support
Community Support

Hi @IanCockcroft ,

 

Enter the workspace where the dataset is located and click settings.

test_Disabling gateway refresh.PNG

 

Best Regards,
Liang
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Hi guys, thanks for you help.

I was able to dig deeper, and its a measure thats not working.

trying to figure out why.

thanks again for taking the time.

lbendlin
Super User
Super User

"The only problem is, when    opening the report in the web service,   it tries  to refresh automatically.  Breaking  some visuals."

 

I don't think that is correct. An unsuccessful dataset refresh does not blit the data over.

 

The way the service works is :

- a dataset refresh request does not work on the dataset itself but on a shadow copy. 

- only if the refresh is successful it will swap the new dataset in and the old out (blitting)

 

So your failed gateway based refreshes are unfortunate for the service performance (wasting resources) but they have no impact on the existing dataset.

Thanks Ibendlin, we just assumed it was the gateway because we gettin an error.

 

The crux of the proble is that certain visuals are not working and thats actuall what we are tryng to solve.

It must/might be for a totally different reason.

Helpful resources

Announcements
Fabric Data Days Carousel

Fabric Data Days

Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!

October Power BI Update Carousel

Power BI Monthly Update - October 2025

Check out the October 2025 Power BI update to learn about new features.

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Kudoed Authors