https://communities.bentley.com/products/road___site_design/f/geopak-inroads-mx-openroads-forum/172520/corridors-becoming-corruptI have 2 general questions. I have been having some issue with my corridor files becoming corrupted. I was told that it may be that I may have &quot;snapped&quot; to a reference file when creating the corridor. The snaps create a connection between the corridoren-USTelligent Community 12https://communities.bentley.com/thread/497303?ContentTypeID=1Tue, 18 Dec 2018 14:48:39 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:2a198466-f29f-4135-8382-c1320ddd0b1bBrian Nilson<p>Thanks Robert. That info very helpful.</p><div style="clear:both;"></div>https://communities.bentley.com/thread/497298?ContentTypeID=1Tue, 18 Dec 2018 14:32:50 GMT6dad98f5-dbc9-4c4d-a9ba-e9da8dc6aa8e:f82c837b-ecfd-496c-8836-a465136d3d7dRobert Garrett<p>Brian:&nbsp; Snapping to reference file elements is a legitimate workflow and shouldn&#39;t cause corruption of the corridor.&nbsp; What causes problems is if you later detach the reference file. After detaching the reference file, the corridor now knows it needs to update itself based on the snap rule, but the thing snapped to cannot be found.&nbsp; The corridor is (probably) not corrupt but it cannot update itself.&nbsp; Reattaching the reference file should fix the problem.</p> <p>Having said all that, I have seen simple things like snapping cause crashes and worse. One of those sad but true sorta things.</p><div style="clear:both;"></div>