In large ACC projects with multiple disciplines, data drops, or phase folders, a version upgrade can easily involve hundreds of cloud models.
In our case, there were about 850 models totaling 130 GB.
Currently, the automatic cloud upgrade process runs strictly sequentially and treats the entire project as a single operation.
It would be extremely useful if users could:
prioritize or order specific models for upgrade,
see a clear progress and status overview (e.g. “in progress”, “completed”, “failed”),
exclude, pause, or cancel individual model upgrades,
and re-run only failed models without restarting the entire process.
At the moment, if even a few models fail, the entire upgrade is marked as unsuccessful — even though hundreds of others may have been converted successfully.
This can result in several days of downtime without any way to intervene.
Additionally, displaying the Revit version as a metadata attribute in ACC would make it much easier to identify which models require upgrading beforehand.
It would also be very helpful if error messages in the upgrade report were more descriptive.
Currently, the message “The following errors could not be resolved by the upgrade service. These must be fixed manually before the upgrade can complete.” provides no clear indication of the root cause or how to resolve it.
Ideally, each error should include a specific description or at least a link to Autodesk documentation explaining how to fix or prevent the issue in future upgrades.
Artur Szymanski
auxalia WESTCAM Group
