@RSomppi, I appreciate that my reply above isn't helpful. I only know that it's something that frequently hampers my colleague and I. It has happened under varying circumstances, so I can't provide step-by-step instructions to reproduce it -- rather it seems to happen for a variety of reasons that don't seem to make themselves apparent.
Most recently (this morning) it happened after adding a structural connection (base plate) between a column and pad footing. That didn't cause the error, but copying the entire column-baseplate-footing to create a second instance more than once fails because of the ' background calculations'. I'm not copying dozens of columns, so I don't think I can be somehow overloading Revit -- but even if were, the fact that no amount of waiting to let Revit catch its breath makes any difference. The ONLY solution I have found is to continue the cat-and-mouse game of opening and closing another file just to get Revit to inexplicably stop calculating. I don't know how this could qualify as a 'self-inflicted' issue any more than any other bug -- I'm just using the program in a way that Revit allows, and it frequently doesn't work.
If I sound frustrated, and lacking a constructive attitude about this, it's because I've consistently seen AutoDesk ignore requests time and time again. The only thing I've ever seen them actually fix was the low-contrast interface that came with Revit 2024 -- and that took them months to even acknowledge, despite considerable input from customers. I'm amazed by how many times I go to search for a solution to some bug I'm experiencing only to discover the google search results come from AutoDesk forum posts from more than 10 years ago -- which hardly gives me confidence to spend my time asking AutoDesk nicely.
I'm not proud of ranting, but sometimes AutoDesk make me feel that's the only thing I can do.
