RESOLVED- "We're unable to synchronize your projects" issue identified
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
**UPDATE 6/9/17 - The issues below have been completely resolved and both new/previous users of CAM Cloud Libraries should not be seeing any problems. Thanks for your patience!
UPDATE 2:30pm PST, 6/7/17 - We've fixed the data panel project listing issue ("We're unable to synchronize your projects") mentioned below. However, there will still be issues using the CAM Cloud Library functionality, including a potential crash when trying to access them through the data panel, for users who enabled CAM Cloud Libraries between 5/29/17 and ~2:15pm PST on 6/7/17. We're still working to resolve the issue for those users. NOTE - If you've experienced this crash when accessing your asset folders, you may also run into a crash happening cyclically upon start-up due to Fusion trying to automatically access this folder. To fix this, please follow the steps to reset your data panel manually per this link here.
--------------------------------------------------------------------------------------------------------------------------------------------------
F360 Community - We recently discovered that enabling the CAM Cloud Library functionality is causing problems with projects, which in turn means the Fusion 360 data panel may not show an accurate project listing. This is occurring for any user who first enabled CAM Cloud Libraries in their preferences after May 29th,2017 - if CAM Cloud Library functionality was enabled prior to this date, you should not be seeing this problem. If you're impacted, here is what you can expect to see: “We’re unable to synchronize your projects”
This has been flagged as a high priority issue and we are currently working on a solution. We anticipate releasing the fix within the next 48 hours, and in the interim, suggested workarounds are to access data through Recent Data or to switch to Offline mode. If you haven't yet enabled CAM Cloud Libraries, we suggest holding off until a fix has been deployed.
My apologies for the disruption, and sincere appreciation for those of you that have helped our support and development team track down the issue.