Forum Discussion
Loading spinner keeps spinning after publish
About 1/3 of the times when I publish changes to a Dataflow Gen 2, the loading spinner just keeps spinning after I click the publish button.
I am able to work around this by closing the dataflow, reopening the dataflow, then make the same changes one more time, and publish again. Then the changes gets published. But it takes extra time for me to make the changes again.
Hi fabricator1
If you want to report an issue then I will request you to please go ahead with Microsoft support on this.
https://support.fabric.microsoft.com/en-US/support/
Thanks
6 Replies
Hi fabricator1
Thanks for using Fabric Community.
Apologies for the issue you have been facing. This is a known issue in Microsoft Fabric. Failed dataflows show in progress refresh history for some tables, while it's not refreshing anymore.
The work around is to retry to refresh the dataflow again and check the refresh history.
For more details regarding this know issue please refer to this link: Link1
Our team is continiously working to fix the issues. This will be fixed soon and I will keep you updated.
You can also refer to this link for known issues and get the updates related to Fabric: Known Issues
Hope this helps. Please let me know if you have any further questions.Thank you for the reply
My issue is not regarding refresh. My issue is regarding publish.
Many times after I press the publish button in a Dataflow Gen 2, nothing happens. The loading spinner just keeps spinning. I am still in the Dataflow Gen 2 user interface, not getting redirected to another page.
I am able to work around this by closing the dataflow, reopening the dataflow, then make the same changes one more time, and publish again. Then the changes gets published. But it takes extra time for me to make the changes again.Hi fabricator1
Thanks for explaining the issue. There is also a known issue related to Dataflow Gen2 publish: Link1Apologies for the issue you are facing and I request you please share the feedback on our feedback channel . Which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
Hope this helps. Please let me know if you have any further queries.
Hi fabricator1
We haven’t heard from you on the last response and was just checking back to see if you got a chance to post your feedback. Otherwise, will respond back with the more details and we will try to help.
Thanks
