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! Request now

Reply
Anonymous
Not applicable

DAX running slow

First date below 90% bookings =
Hi,

 

I have below dax and it gives the error: operation was cancelled because of locking conflicts.

 

Can you please help on how to optimise it and avoid the error.


VAR newtable =
ADDCOLUMNS (
SUMMARIZE ( Job, 'Booking'[County],'Booking'[Location Code],'Date'[Date]),
"@ratio", Job[Booking %]
)
VAR filtertable =
FILTER ( newtable, [@ratio] < 0.9 )
RETURN
IF (HASONEVALUE('Responsibility'[Name]), (MINX ( filtertable, 'Date'[Date] ) ), BLANK())

1 ACCEPTED SOLUTION
Anonymous
Not applicable

Hi @Anonymous ,

 

If you’re making changes to your dataset (for example editing the DAX for a measure) in Power BI Desktop then Power BI has to wait for any DAX queries, that is to say the queries that get the data for your visuals, that are currently running to finish before it can save those changes. However if it has to wait too long to do this then it will kill any queries still running so it can go ahead and commit those changes, and when it does so you’ll see the “locking conflicts” error. 

Since the problem is caused by long-running DAX queries the answer is to tune your queries to make them faster.

Refer: https://blog.crossjoin.co.uk/2021/10/31/understanding-the-the-operation-was-cancelled-because-of-locking-conflicts-error-in-power-bi/ 

 

Best Regards,

Jay

View solution in original post

4 REPLIES 4
Anonymous
Not applicable

Hi @Anonymous ,

 

If you’re making changes to your dataset (for example editing the DAX for a measure) in Power BI Desktop then Power BI has to wait for any DAX queries, that is to say the queries that get the data for your visuals, that are currently running to finish before it can save those changes. However if it has to wait too long to do this then it will kill any queries still running so it can go ahead and commit those changes, and when it does so you’ll see the “locking conflicts” error. 

Since the problem is caused by long-running DAX queries the answer is to tune your queries to make them faster.

Refer: https://blog.crossjoin.co.uk/2021/10/31/understanding-the-the-operation-was-cancelled-because-of-locking-conflicts-error-in-power-bi/ 

 

Best Regards,

Jay

Anonymous
Not applicable

I am using live connection to a tabular model.

Anonymous
Not applicable

I am using live connection to a tabular model.

Samarth_18
Community Champion
Community Champion

Hi @Anonymous ,

 

Could you please let us know which type of connection mode you are using composite or direct query?

 

Thanks,

Samarth

Best Regards,
Samarth

If this post helps, please consider accepting it as the solution to help the other members find it more quickly.
Appreciate your Kudos!!
Connect on Linkedin

Helpful resources

Announcements
November Power BI Update Carousel

Power BI Monthly Update - November 2025

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

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!

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 Solution Authors
Top Kudoed Authors