Forced Disconnections when reloading configuration

[Tye Austin]

Sometimes, if I need something added to the services and after I get them added to the database by our database guy, I will get a lot of forced disconnections when I reload configuration.  sometimes it's none.  sometimes a bunch.  I just had 650....   that was too much for me to not now need to look into what is causing it.  Anyone know if this is an easy thing to manage when the database is being modified/managed?  I found one Autodesk support page on it but it didn't have a lot of info besides saying they resolved it in 22.  which they didn't.  I've had it happen in all years of Revit.

[craigjonnson]

It is a common issue and im told its fixed in 2026, which would be years away from us using on projects. I dont know of any fixes or what causes it, i dont believe its a database issue given that Autodesk has looked at this on the software side.

[chris4455]

We also get that.  We recently were having issues reloading the configuration on a large project where it would crash Revit.  I tried reloading about 4 different ways and nothing was working.  Finally I gave it one more chance and I opened a small view and turned off the piping/ventilation worksets and it reloaded without crashing and had minimal disconnects.  I'm not sure why it worked this way but I'll take it as a win. 

[Tye Austin]

We also get that.  We recently were having issues reloading the configuration on a large project where it would crash Revit.  I tried reloading about 4 different ways and nothing was working.  Finally I gave it one more chance and I opened a small view and turned off the piping/ventilation worksets and it reloaded without crashing and had minimal disconnects.  I'm not sure why it worked this way but I'll take it as a win.

That's interesting.  I wonder if we turned off all worksets before reloading, we would maybe also have less issues.  I'll try that next time and report back.  trouble is, it's pretty inconsistent on whether it does the disconnects or not or the amount.

[rjdonahue]

I wanted to chime in on this, the solution from chris4455 seems to be the answer for our projects. I have tried this with several very large projects that have been plagued with this error, and closing the piping/ductwork worksets we model on before we reload config has given no disconnects. Hopefully this continues to work. Thanks!!

[Darren Young]

What causes the disconnect? Primarily Autodesk.

Sure, there's things you can do that make that happen. One of the more common ones is changing Connector breakpoints. That means parts will need to be spaced further/closer together and Revit won't magically "move them".

As an example, if you had back to back welded fittings and changed the weld gap from 1/8 to 1/16... Revit doesn't try to throw in 2 seperate 1/16 welds and a 0 length piece of pipe. but it also won't move the fittings either.

We've dealt with this since 2016. Each time.. "we can't reproduce it" only for them to make it a little better each release. But they always blame database changes.

It wasn't until I showd them a reload (4-disconnects) followed by another reload (2 more disconnects) that they seemed to believe me.

And it use to also often remove parts. So I know they spent a LOT of time making sure things don't delete and don't disconnect unless it truely physically needs to.

Should we as customers need to do this? No. But sometimes you do need to persist and provide them years worth of examples and evidence to get these things fixed.