Skip to main content
Solved

The Instance Update Keeps Reverting to Older Version

  • October 10, 2025
  • 3 replies
  • 101 views
Herza

I experience the same issue as that! But that topic has been closed for reply.


This is the latest version of my ticker component, with variant:
- Info
- Success
- Warning
- Error
- Waiting
- Tip

But if I copy that component (as intance) to other page, like this:

 


As you can see in the picture above, the update icon in the top right corner is active (blue), which shouldn’t be. Because the instance has just been newly copied here using the latest instance directly from the source.

If I open the “Variant” options, it still correctly shows the variant list which is the latest variant list:


But if I update the component by clicking the update icon, it reverts to old version (as depicted in screenshot below) where:
- There was no “Tip” variant that should exist in the latet version
- There was “Awaiting Review” variant, which has been removed in the latest version
- There was “Multiple Awaiting Reviews” variant, which has been removed in the latest version

​​​

 

I have followed the instruction here to clear the cache
https://help.figma.com/hc/en-us/articles/22380853110551-Clear-the-Figma-desktop-app-cache
But that issue persists.

I also noticed something wrong in the component when I tried importing the component from “assets” in the left sidebar instead of copy-pasting: the latest update was “16 days ago”? I just published the update like several minutes ago.
Then I tried removing the file in the assets list, and readded it again. And the issue persists. Seems like… the issue is, the component update is not admitted?
Creating a new component to replace this one isn’t feasible, as it’s widely used across my design system. Please help address and solve the issue rather than ask me to discard the component.

 


Apparently, it is not platform specific issue. I use desktop app, but I tried it on web and it encountered the same issue.

Best answer by Herza

Hello ksn. It seems to have been fixed by now. What I did to fix it was remove all unusued properties in the main component, then when published, it became normal again, no issue. Is that supposed to happen, that unused properties block components update sync? Well if that is supposed to happen, users should be explicitly informed. Thanks for your response, anyway. Really appreciate it.

3 replies

ksn
Figmate
  • ksn
  • Community Support
  • 2041 replies
  • October 13, 2025

Hey ​@Herza - happy to help get you the help you need. First, just to touch base on the original post you mentioned: it is an older one from about a year ago, so it was closed due to age.

However, it doesn’t mean that your issue isn’t still relevant and valid (I just wanted to give some context behind the closed topic).

 

I also noticed something wrong in the component when I tried importing the component from “assets” in the left sidebar instead of copy-pasting: the latest update was “16 days ago”? I just published the update like several minutes ago.


Then I tried removing the file in the assets list, and readded it again. And the issue persists. Seems like… the issue is, the component update is not admitted?

 

Yeah this does sound strange -- I’m not quite sure why the audit shows the update being so far off, and unfortunately, I’m not equipped with the tools to see more than the surface-level information you’ve screenshotted and provided here.

 

Are you able to share the file you see this in? If that’s possible, please do the following:

  • Share edit access to all the relevant files with support-share@figma.com. This is our official Figma support account, and only select support and engineering members will be able to access them to try and replicate any problems. You will also not be charged for this.
  • File a help ticket here, and include a direct URL to the file[s] you’ve shared access to.

Once you’ve done that, please let me know and I will escalate it for further assistance.

Herza
  • Herza
  • Author
  • New Member
  • 3 replies
  • Answer
  • October 15, 2025

Hello ksn. It seems to have been fixed by now. What I did to fix it was remove all unusued properties in the main component, then when published, it became normal again, no issue. Is that supposed to happen, that unused properties block components update sync? Well if that is supposed to happen, users should be explicitly informed. Thanks for your response, anyway. Really appreciate it.

ksn
Figmate
  • ksn
  • Community Support
  • 2041 replies
  • October 16, 2025

Hey ​@Herza - thank you for the response, and letting me know that this had been resolved.

From my current understanding, I don’t believe this should be the case -- it may have been a weird blip. If you run across this again when resetting, let me know.

I marked your response as the best answer, since you did mention a solution that fixed this on your end. Feel free to create a new topic if anything else comes up.


Terms & ConditionsCookie settingsAccessibility statement