I’ve been experiencing this for months. did sync & unsync, publish & unpublish, and don’t ask how many times I had install & reinstall. but it still doesn’t work. the above is my screenshot on figma working file, below is the screenshot on my design system. on the working file it doesn’t updated, why is that? (in philomena accent)
Hi
This definitely seems odd, so I completely understand how this must be affecting your workflow. You mentioned that this has been happening for months. Were your collections being updated as expected previously? When exactly did you start running into this issue?
With a few more details, we can try to investigate what’s happening together.
I have encountered the same issue. Currently Collection Names will not be updated.
Hey
The same additional context is needed, so our team knows where to start their investigation. Were your collections being updated as expected previously? When exactly did you start running into this issue?
Again, with a few more details, I can escalate this issue to our team to investigate.
Hi
I have this exact problem. It has always been an issue for a very longtime however…
Yesterday I changed the name of one of my modes in a collection, re-ordered another mode to be the default (placed in the first mode column) and published. This actually caused a whole host of issues that look as though the cache / variables get totally confused. But staying on point I did not see the collection names update. The collection names have always been a little flaky and sometimes show old names from months and months ago. It is only because I can remember the old names and how they map to the new ones that I can still use the themes.
Today I came back in and the newer names periodically appeared and then reverted back to the some very old ones. I restored my main design system library to before I made the above amendments, published and now still have old names.
The collection naming synchronisation just does not work consistently and in most cases never updates to finally be correct. Any help would be great. I would be happy to go on a video call and share this with you but I cannot publish any material here.
Many thanks
Thanks for the additional context,
I relayed this to the team, and they confirmed that this is related to a long-standing bug that they’ve been trying to fix. We don’t have an exact timeline we can share right now.
As a first step and temporary solution, try to ensure that you’re not using any outdated versions of the not updating collection in your current file (these will be the ones that show the old/previous name). Be sure to consistently accept any updates in your subscribed files to the the updated Collection as well to see if that helps.
While I wish there was more we could do here, these are the only manual steps you can try to help mediate the issue for now until we have a full solution ready.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.