Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!
Hi @chang_B
It’s a known issue . The engineers are actively working on this issue and I will come back with an update if there is any progress.
Best Regards,
Community Support Team _ Ailsa Tao
Existing ICM for similar issue(ICM 297756751). It should be a new known issue that dataflow refresh taking long times that usual to complete. Employee engages this issue as well.
Hi @TiCordeiro
This issue has been submitted to ICM , the ID is 343344031 . If there is any progress, I will come back to update .
Best Regards,
Community Support Team _ Ailsa Tao
Currently it have been considered as a known issue which would be fixed in early of September, so please stay tuned.
Best Regards,
Community Support Team _ Yingjie Li
Currently about the fix release for different clusters in this issue that you can refer(as expected):
You can find your cluster in the cluster url from the error message.
In addition, you can try the workaround provided by @Felix4356 which would be helpful:
Open all report builder reports in your workspace, you can use a right click to open each one to separate tabs in your browser. No need to run each one, just close each tab that you just opened. Then publish
Best Regards,
Community Support Team _ Yingjie Li
Hi,
Have you turned on the “Power BI Desktop infrastructure update preview feature” in the desktop setting?
If so, a similar issue has been reported internally, so stay tuned.
Problem description: When trying to launch Power Bi Desktop, it throws a frown error when the Power BI Desktop infrastructure update preview feature is enabled but if we disable this feature PBI Desktop launches as expected.
ICM: 279388210
As a temporary workaround, I suggest you to go to the setting to turn off the option “Enable infrastructure update preview feature” to make this issue disappear:
I will update here once I get any information.
Thank you very much!
Best Regards,
Community Support Team _Robert Qin
Hi @karma123 ,
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_Scott Chang
There is the same issue here and you can find the expected fix date about it and potential workaround:
https://community.powerbi.com/t5/Issues/Issue-Can-not-publish-power-bi-app/idc-p/2668626
Best Regards,
Community Support Team _ Yingjie Li
Hi,
A similar issue has been reported internally, so stay tuned. ICM: 274100968
I will update here once I get any information.
Best Regards,
Community Support Team _Robert Qin
Hi all,
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 @Barry_Smart ,
We have submitted to internal ICM 304873937 , the status of this thread will be changed to Accepted to prove that this is a bug confirmed by Microsoft.
We have gotten some feedback from the PG team:
“The cyclic reference is because the record field name is Schema, and the customer is trying to assign the value of Schema to be Schema. This means that in order to evaluate the "Schema" field, the engine first has to evaluate the "schema" field, producing infinite recursion. This is not a problem with the connector, but with the customer's mashup query. Query editor uses different queries to produce (and refresh) the preview data, so the cyclic reference does not become immediately problematic until refresh when the customer's query is ran.
There is a simple mitigation for this: clients may avoid using schemas that have a name called schema, or referencing them from a different schema name.”
The bug has been submitted but there is no clear time frame for fixing it yet. Engineers are trying their best to solve this issue, please be patient and I will give you feedback here once there is any progress.
Best Regards,
Community Support Team _ Caitlyn
Hi @stugardner1037 ,
From the post you shared, the issue appears to be a known issue and is being fixed. You can be patient and wait for the issue to be fixed.
Best regards,
Community Support Team Selina zhu
Hi @Amicci ,
There are indeed users who also have this problem, which has been reported to ICM , the id is 348173711.
I'll be back with an update if there's any progress .
Best regards,
Community Support Team Selina zhu
Hi @tzhang ,
This is a known issue and has been reported to the ICM,the id is 351854979.I'll be back with an update if there's any progress .
Best regards,
Community Support Team Selina zhu
Hi @Anonymous ,
This is acknowledged as an issue.
We have reported the issue and submitted it to the internal icm platform, No: 353858161.
No workaround for now,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
Hi all ,
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 ! Thank you for your cooperation !
Best Regards,
Community Support Team _ Ailsa Tao