Updates in Design System not updating in other files

I believe I am having the same issues. I just recently went through and updated my teams Design system to apply variable values to all of the components. When I go to use the component in another file it is still showing all of it’s original values - no variables applied. It’s even kept properties that I completed removed in the Design system. 

One thing I tried with another component was deleting the entire component (variant group and all) and completely rebuilding it. This seemed to have fixed the issue, but I would like to not do this to every component. 

I may have found a solve. Seems like a weird bug potentially occurring, but unlinking and relinking the design system to the specific file resolved my issues.

Update: Scratch that didn’t work. Some components are totally fine, but then some variations of some aren’t updating properly.

I’m having the same problem.  Sometimes an update of a component flows through to the design file, and sometimes it doesn’t.  This seems to be an issue for me just recently.

I am also having the same problem.  I created some new colors in the library, but when I try to use them they show up with completely different colors.  These are not colors I have ever added to the library.

Hi everyone, sorry to hear you're running into issues with your Design System updates not reflecting in other files!

To cover some basics, here are a few temporary solutions that may help:

•  As ​@BradleyA mentioned, try using the “Repair component connections” in the quick action to see if that resolves the issue.
   
• You can also try the “Regenerate all instances” command (found in the same menu) and check if the instances then update correctly.
   

• If that doesn't help, another workaround is to apply a small change to the main component to trigger an update.
  
  Here’s how:
  - Go to main component, make a minor edit in the component (that you can easily remember and undo afterwards) —like adding a stroke or slightly adjusting font weight.
  - Publish the update.
  - In a different file, accept library updates and insert an instance of that component. Check if the issue is resolved.
  - Return to the main component and undo the test change you made.

  This approach usually helps “reset” the instances / assets and bring them back into sync.

If you’ve gone through these steps and still aren’t seeing the updates in your files, our support team can take a closer look by submitting a bug report.
In the form, please include:

• A link to the affected file with can edit access granted to support-share@figma.com

• A link to the file where your library is located. Please note, granting access to this support account will not affect your seat count or incur any additional charges.

• A brief description or a short video showing the issue
  Thanks!

Tried all solutions from this thread and still not working for color variables. My Case:

FIle A - updating color Variable 1

File A - publish changes

FIle B - no library update visible

File B - component X with Variable 1 still have color hex not updated, but it has the same variable name. after manual  giving Variable 1 color is changing

Tried the same thing with string Variable (for fonts style) - after updating File B, changes are made automatically for component X

Same issue. Only way to update a component is to delete the instance and re-insert the same component from the library. Reset or any amount of time does not solves the issue. I have the same issues with all types of assets. Colors, tokens, new items. for all my instances. The issue is not within the same file, just linked files. 

A solution would be much appreciated :)

Hey everyone, thanks for flagging this, and sorry the workarounds haven’t helped in your case.

Since this is affecting multiple asset types across linked files, the best next step is for our support team to take a closer look. When you have a moment, please reach out to them with a link to a copy of your file (and grant edit access with support-share@figma.com) and the steps you’ve already tried. That will help the team investigate what’s going on more effectively with you specific case.

You can submit a ticket here: Submit a bug report. Thanks again for your patience!

​@Celine_  I’ve spent the last 15 minutes trying to submit a bug report. After dealing with countless pop-ups and searching through multiple AI bot suggestions and topic-based solutions, I’ve given up. I understand the need to streamline or filter requests, but this level of complexity is unlike anything I’ve seen before.

Is there a direct email address or a simple way to send in my request? Getting support shouldn’t be this difficult.

Sorry for the disruption here, we’re actively reviewing the support form experience, and your feedback is really valuable. I’ve shared it internally with the team.

I’ve also created a support ticket on your behalf. Your ticket number is #1606798.
Please check your inbox when you have a moment (I sent it to your address mail: bixxxxxy@mxxxo ). Feel free to add any additional details directly in your case so the team can take a closer look. Thank you!

Came here to say I’m having an issue with components updating from my main library to one of my connected files too. The only thing that seems to work is to close and re-open Figma every time I make an update, which is quite time consuming and frustrating. I’ve tried workarounds, and refreshing the page. ​@Celine_ Do you have a timeline for when this issue will be fixed?

Thanks!

Hi there!
For UD ved Christian’s case, it looks like the issue is caused by pending library updates. To keep all instances in sync, make sure to accept any pending changes under Updates each time something is published (whether assets were added, removed, or modified). Once those updates are accepted, your file and its instances should stay aligned.
As a reminder, you’ll see a blue dot on the library notification whenever there are changes waiting to be accepted. Accepting them will update all affected instances across the entire file, not just a single page.

​@Chrissy Pipetti, could you also check for pending updates on your side? If this doesn’t resolve the issue, your case may be different. In that situation, I’d recommend submitting a bug report so the team can take a closer look.You can follow the steps here to submit a bug report:
https://help.figma.com/hc/en-us/articles/360041468234-What-to-share-in-a-bug-report-to-Figma-Support , or within Figma by selecting the question mark icon in the bottom-right corner of any page and selecting Contact support. Thank you