Power BI is turning 10, and we’re marking the occasion with a special community challenge. Use your creativity to tell a story, uncover trends, or highlight something unexpected.
Get startedJoin us at FabCon Vienna from September 15-18, 2025, for the ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM. Get registered
We are experiencing an error creating a new sematic model as follows:
Another user operation is already running. Wait for a few minutes, then refresh and try again.
Note that I can create the new model in our Bronze layer but recive this error in our gold layer.
Please help.
According to Microsoft support it is part of a bigger known issue with Direct Lake.
Other symptoms are when you do get the new model created tables that are in lakehouse do not appear for 24 hours and you can only add a few at a time if they do exist. Of you try to add more you get this error again regardless of running pipelines, notebooks etc.
Basically you have to do it bit by bit by bit adding tables over a number of days to build your new direct lake semantic model. Crazy.
Thanks for confirming, this has been driving me crazy and consuming much time that i do not have.
Fabric is great, but it is very very rough around the edges. This is dogfooding at its worst.
Rough around the edges is an understatement.
Have you seen the Latency issues between tables queried in PySPark versus the SQL Endpoint? We have had delays of upto 20 hours on that where data existing in PySpark has not updated in SQL Endpoint. Add to this that Fabric support is terrible and you have a fantastic product that really is not fit for purpose yet.
Tried to log a support request but it demands a premier support contract.
This could mean us backing away from Fabric for 12 months until its base functionality is at least somewhat stable.
DataBricks and Synapse SQL Serverless don't do these things but then again alot of functionality is not in those products.
We have spent alot of money on Fabric and our pilot projects are causing us to have to come up with lots of inhouse workarounds which only adds to frustration.
Hi @Sureshot ,
Is my follow-up just to ask if the problem has been solved?
If so, can you accept the correct answer as a solution or share your solution to help other members find it faster?
Thank you very much for your cooperation!
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi @Sureshot ,
The error message “Another user operation is already running. Wait for a few minutes, then refresh and try again”, which usually indicates that concurrent operations need to be completed before continuing.
Check if the corresponding location in Monitor has In Progress processes.
You may want to check with your team to make sure that no one else is performing the task that may be causing this conflict.
Clear your browser's cache and cookies, then close your browser and reopen it.
Check these steps and then contact me.
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
This is your chance to engage directly with the engineering team behind Fabric and Power BI. Share your experiences and shape the future.
Check out the June 2025 Fabric update to learn about new features.