Content Catalog problems

[jrathLHK5W]

I am having extensive problems with content catalog. Menus not working, thumbnails not uploading and now 2 months of work uploading files is out the window. All of my content is gone ... wiped out this week ... Autodesk started out with working software and they broke it very badly.

[Ric_Weber]

Jeff, 

I understand your frustration with that process.  Autodesk is aware of those issues and is working to correct the issues that are requiring the log out, clear cache, log in procedure.  You should definitely not need to do that often. 

If you were/are a legacy Unifi subscriber, I would definitely recommend sticking with that for a while yet.  Please keep testing CC to help with development, but at the moment there are so many more features in Unifi than are available with CC yet.  I believe they are planning to update Unifi to work with Revit 2026 also, but don't rely on my statement as I am not Autodesk.  To my understanding anyone that had Unifi previously are still able to use that.  If that is the case and it is not working for you, I'd recommend issuing a support ticket.  Someone should be able to help out.  

[jrathLHK5W]

nope ... content catalog hangs up in R22 and R23

[jrathLHK5W]

OK ... it looks like this is a variation of the same bug that BIM 360 had about 7 or 8 years ago. I would access BIM 360 with Revit 2018 and if I exited without logging out and then went and opened Revit 2016 or 2017 I would be locked out of Bim 360. They still have the same flaws built into the source code and they probably just patched it with a fix instead or eliminating the flaw.

[Ric_Weber]

Are you using the "Launch as app" or "Launch in browser"?  Have you tried opening a new browser window, NOT from within Revit, and going to contentcatalog.autodesk.com (or contentcatalog.autodesk.eu) and try using it from there?  I would definitely issue a support ticket for this issue.  This is not normal and is not happening to most people.  

[jrathLHK5W]

launch as app and launch in browser are just 2 different ways for it to fail ... I usually us app

[jrathLHK5W]

I do have an open support tick that is ongoing

[jrathLHK5W]

Yes I wish I had access to Unifi ... that actually works.

[Ric_Weber]

@jrathLHK5W  So have you tried not doing either then and just going to your browser, (Edge or Chrome) and going to www.contentcatalog.autodesk.com and signing into CC there and using that?  

[jrathLHK5W]

yes that also fails ... the sign out and sign in trick is the workaround

[j.muntz]

This worked for me.

help article: https://www.autodesk.com/support/technical/article/caas/sfdcarticles/sfdcarticles/Library-items-are-... 

Causes:

Issue with web browser cache.

Solution: To address this behavior, do one of the following procedures:

Update Content Catalog:

Install the latest version of Content Catalog.

Clear the browser cache:

1. In the web browser open the Developer Tools. Use one of these methods:

   • Right-click anywhere on the web page and select 'Inspect'. 

   • Click the Settings button (might be an icon with 3 dots) > go to More tools > Developer tools.

   • Hold Ctrl+Shift+I.

2. In the sidebar that appears, navigate to the Application tab, then to Storage on the left side.

3. Check the box that says, "including third-party cookies".

4. Click "Clear site data".

5. Click and hold on the browser's refresh button, hover over Empty Cache and Hard Reload, then release the click.

6. Once the site data is cleared, re-launch the Content Catalog web page.

Clear the browser cache, site data, and authentication tokens associated with signing in:

1. Open Google Chrome.

2. Go to ACC home page.

3. Click your profile picture, then Sign Out.

4. Go to the Chrome settings (three dots button in top right).

5. Go to More Tools > Developer tools.

6. When a new sidebar pops up, click the Application tab at the top.

7. Go to Storage on the left side.

8. Under the Usage pie chart, check the box for "including third party cookies".

9. Click Clear site data.

10. Click and hold the refresh button in the top left of the window next to the forward/back buttons.

11. In the drop-down menu, pick Empty Cache and Hard Reload and release your mouse button.

12. Close out of the Developer Tools sidebar.

13. Close all Chrome windows.

14. Reopen Chrome.

15. Go back to ACC home page.

16. Sign in.

17. Repeat the above steps with Content Catalog page.

[jrathLHK5W]

that did not work for me ... what works for me is every single session of Revit do not exit before logging out and every single session of Content Catalog do not exit before logging out. It is a cumbersome workaround that will overcome the flaws in the source code of Sutodesk Docs and the flaws in Content Catalog, and the flaws in Revit, and the flaws in the Autodesk identity manager.

This is very similar to the old flaw in BIM360 about 8 years ago.

[Ric_Weber]

Oh man Jeff, that sucks.  That is not normal behavior and you shouldn't have to do that all the time.  You're right, that would be a total pain in the butt.  Let us know what the final outcome of your support ticket ends up being.  Thanks!!

[jrathLHK5W]

yes ... but at least I can get it to work in R22, R23, R24, and R25 by doing the cumbersome workaround

[jrathLHK5W]

ok ... after further testing I determined that I only have to logout of Content Catalog and not Revit. And if I forget to logout when running 22 or 23 then I have to open 24 or 25 and logout then I can go back to 22 or 23 and open content catalog

[M_Waiton]

I am having loads of issues with the Content Catalog. No Pending Approvals are showing even though I know that there are items waiting to be approved.

I have logged out, reset, tried Chrome, Edge and the app versions and nothing is coming through!

[v.boreux]

I'm checking in for an update on these issues.

I'm also facing a bunch of frustrating issues:

• I installed the latest version of the plugin, and now the 'Insert' button does nothing!

• My uploaded families are still split between French and English category names. I insist that all the families I uploaded were created based on a French template.

• I haven't verified this with the latest version, but I still have some users who were never able to get out of the "login loop of hell."

It's been more than a year since I teased the Content Catalog in my office, and I still can't deploy it, which is quite frustrating.

I spent a certain amount of time preparing my catalog by tagging and creating collections, and I'm afraid part of the solution will be recreating all of it under a newer version of CC to get things straight... Maybe I'll just drop the whole thing at this point.

[Ric_Weber]

@v.boreux, you should definitely be submitting support tickets for those items. Those are not the norm and are not happening to everyone or anyone that I've heard about, something is amiss.  I'd suggest three separate tickets so they can divide and conquer so to speak.  

[phil.mundell]

We are having a "similar" issue to those in that thread (I didn't want to clutter up and make a new one),  in that when a different version of Revit is used to insert the updated families, it inserts the older versions of the family instead, unless I (as admin) completely delete the family and readd it to the library.  If you use the same version of Revit as the family was created in, then it appears fine. 

Everyone is using the browser to access the library and not the app and it does very much sound like a caching issue but I am unsure if this is simply something that will resolve itself once the model update has done what it needs to do at server end (EU) or if I genuinely do need to delete the family every time. 

[Ric_Weber]

@phil.mundell, you don't mention if you have already put in a ticket or not.  I just tested everything out.  It seemed to work just fine for me.  Could you give a step by step of an example of what it is you're trying and what you're seeing.  Here is the test I performed: 

1. Created a test family in 2022
2. Created a test project in 2022
3. Loaded the 2022 family into the 2022 project
4. Exported the 2022 family into CC
5. Opened the 2022 project in 2024 and saved as 2024 version.
6. Edited the family, loaded it back into the 2024 project.
7. Exported the updated family into CC
8. I now have two base versions in CC.  The image looks like the updated version (which is slightly concerning, but really it can only show one image, so that could be expected.  That would be a good idea for CC to show different images if there were multiple base versions)
9. Open Revit 2022 again, insert the family into a new project and it inserts the 2022 version.  
10. Open Revit 2024 again, insert the family into a new project and it inserts the 2024 version.  

So for me, everything seems to be working fine. 

[phil.mundell]

Hi Ric, 

For me, what I am seeing is this;

Step 1
1.Created a family B in 2023
2.Uploaded family B to Content Catalogue
3.Added family B to 2023 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) - Successfully
4.Added family B to 2024/2025 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) - Successfully

Step 2
5.Updated family B > B1 in 2023
6.Uploaded family B1 to Content Catalogue (now shows file history)
7.Added family B1 to 2023 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) - Successfully
8.Added family B1 to 2024/2025 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) but get family B - Failure

Step 3
9.Delete family B1 completely from content Catalogue
10.Uploaded family B1 to Content Catalogue as new file
11.Added family B1 to 2023 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) - Successfully
12.Added family B1 to 2024/2025 project from CC (uploaded family shows 2023,2024,2025,2026 versions available) - Successfully

I shouldn't have to do Step 3 at all. However from reading your post, are you suggesting I need to do the family upgrade for each version and upload them all? If so what is the point of the "Revit Year" drop down box that shows every version of Revit beyond the version the file was created in?