Autodesk Construction Cloud – Clash Issue Data Missing

[Dawid.L]

Hi everyone,

I'm encountering a problem with Autodesk Construction Cloud (ACC) related to Clash Issues.

For some reason, ACC is losing the clash data in created clash issues, and I can't figure out why. Here are the details:

• The file name remains the same across versions

• The shared view name is always the same

• The Element ID does not change

• The GUIDs of the elements are also unchanged

I’ve used the Compare feature in ACC to verify this, and it confirms that there are no changes to the IDs or GUIDs of the elements involved.

We’re working in a local LAN worksharing environment. Before uploading to ACC, we detach the central model, create a clean copy, and then upload that version to the cloud.

As part of our workflow:

• Architects upload their model to their designated folder on ACC

• Our BIM team reviews the file in that folder for quality control

• After review, we copy the file into the folder connected to the Model Coordination module

Even with this structured process, some clash issues lose their clash data after updates. Specifically:

• The issue pin is still visible and correctly placed in the model

• The camera position is retained and works as expected

• However, the clash itself is not resolved and appears as missing

• In the Clashes tab of the issue, ACC shows a message stating that clash data is not available

Additionally, in one instance we updated only one of the coordinated models, while all other models remained unchanged — and the problem still occurred. This suggests the issue is not caused by changes in the other models.

Has anyone else experienced this issue or know what might be causing it? Any ideas on how to prevent this would be greatly appreciated.

Thanks in advance,

[Dawid.L]

Update – Root Cause Identified: Coordination Space Treats File Sources Differently

I managed to figure out why our clash issues were randomly losing their clash data in Autodesk Construction Cloud (ACC), and I’m sharing it here in case it helps someone else.

What was happening

The problem was related to how models were added to the folder connected to the Model Coordination space.

ACC treats files differently depending on whether they are:

1. Uploaded directly into the coordination folder, or

2. Copied from another ACC folder into the coordination folder.

If you mix these two methods for the same model, clash issues can lose their clash data.

Our specific scenario

• First, we uploaded the model directly into the coordination folder.

• We ran clash detection and created issues based on those clashes → everything worked as expected.

• Later, instead of uploading a new version directly, we copied the updated model from another ACC folder (Our partner one) into the coordination folder.

• After that, the existing issues:

  • Still had their pins in the right place

  • Still had the correct camera position

  • But the clash data was gone, and the Clashes tab said clash data wasn’t available.

When we then uploaded the next version directly again (instead of copying), the clash data for those issues came back.

Conclusion / Recommendation

To avoid losing clash data on issues in Model Coordination:

• Do not mix file input methods for the same coordination model.
• Stick to one consistent method of feeding models into the coordination folder:

Either always upload directly, or

Always use copies from another ACC folder, but don’t switch back and forth.

Once we adopted a single, consistent method (direct uploads), the issue stopped occurring.