Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.
We got the feedback from PG team
"After further investigate,Customer needs to work with their internal network team."
Hi @ThuJa23 ,
We have submitted to internal ICM 308260410 , engineers are doing their best to fix this issue, please be patient and I will give you feedback here once there is any progress.
As a workaround,you can try add ?newManageGatewaysUI=false In the address bar at the top of the manage gateway page.
Best Regards,
Community Support Team _ Caitlyn
Hi @mhasan27 ,
We have seen on the internal platform that other engineers have reported this issue and submitted it.
The engineers on the product team are now aware and will do their best to resolve the issue. I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_Caitlyn
Hi @Martin_M
Thanks for your feedback ! I am so glad to hear that you found the workaround . I will change the status to "Delivered" .
Best Regards,
Community Support Team _ Ailsa Tao
Hi @rashidanwar ,
You got a 429 too many request error from the error message, it simply means that there are a lot of requests from the user’s end. When the requests are beyond capacity for the web servers, your browser will crash and display the code.
I suggest you change the time of the schedule refresh, maybe there're other refreshes at the same time. Then, try to clear the browser cache.
Best regards,
Community Support Team_yanjiang
Hi @ocasares
It's a known issue , as @mrtstl mentioned , Microsoft team is working on this issue, please wait for the issue to be fixed, thank you!
Best Regards,
Community Support Team _ Ailsa Tao
Hi @andrecxl ,
We have reported this issue and submitted it to the product team.
They have been aware of the issue and the engineers will do their best to resolve it. I will update here if there is any progress, so please be patient.
Best regards.
Community Support Team_ Caitlyn
Could not reproduce it in my side as far as my test. The paginated report works fine in Power BI Service.
Thanks for @MikeWall provided information that it has been acknowledged as a bug by MS, and we will still continue to investigate this issue, if there is any progress, would update here.
Best Regards,
Community Support Team _ Yingjie Li
The issue has been fixed.
Hi @Brains_86
Does scheduled refresh not work for all datasets ? If you roll back to a previous version, will scheduled refresh still report an error?
Best Regards,
Community Support Team _ Ailsa Tao
Hi @aleckealey18 ,
Please try updating Power BI Desktop to the latest version. Alternatively, you could try using a different connector, such as the ODBC connector that the user has already successfully used, or a third-party connector that is compatible with Snowflake.
Best Regards,
Community Support Team _ Neeko
Hi all,
This is acknowledged as an issue.
We have reported the issue and submitted it to the internal icm platform, No: 353461347. Engineers will do their best to resolve the issue. I will update you here if there is any progress , please be patient.
Best regards.
Community Support Team_ Caitlyn