Hi there! Can you reach out to support@figma.com with links to the library file and the instance file?

We might need to take a look at them to diagnose exactly what’s happening, so please also share those files to support-share@figma.com with edit access if possible. Linking to the exact instance would be a huge help to our team in diagnosing what’s happening here.

Thanks!

Hi! Can you reach out to support@figma.com with links to the library file and the instance file that you reverted?

We might need to take a look at them to diagnose exactly what’s happening, so please also share those files to support-share@figma.com with edit access if possible. Linking to the exact instance would be a huge help to our team in diagnosing what’s happening here.

Thanks!

Sent email and Edit access invite. ✔️

Sent email and Edit access invite.

For me it half-worked.

Firstly I’ve updated as mentioned above and it worked. But after the update of main components i copy/paste one artboard (with components that needs updates) to the new figma file and than updated the components. After the update everything was reset again.

Than i tried to do some small changes for the sake of test, and everything was back to normal.

So I’m not sure if this problem is fixed or not. Because still sometimes Figma reset components after update.

I opened my Library file > Reverted it back to 18 January

I opened one of my Project files > Reverted it back to 18 January > I made sure it was properly linked to the Library file

I made a change in the Library file > Pushed changes

I went back to the Project file again > Updated it with changes made in the Library file

I observed and nothing was overwritten besides the desired change I made.

I made a few more changes, catching up on some work while observing again and nothing got overwritten (success!). I will be doing the same today. BUT

I feel super insecure about my actions on Figma at the moment and that will result in double-triple checking stuff all the time now…

The following requires doing all the work you lost for the past 2 days but perhaps it could be an ok strategy:

• See a version of your Figma file where all work you did yesterday and the day before is visible and intact (using the history feature)


• Save that file manually to your computer


• Rename the saved file to something different (to distinguish it)


• Upload that file to Figma again


• Apply steps described by Figma reverting your work 2 days back (losing progress)


• Now at least you have an easy overview of the work that was lost so you can catch up a little quicker

Hi all! We’ve pushed some updates and additional guidance for users still experiencing this issue. Please check @Josh’s post here for the latest information: Monitoring: Overrides not preserved when library is pushed - #84

Hi guys, I tried the suggested steps plus files refresh, and it seems that everything is working again. Thank you @Josh, @thudson and @anon21722796 👍

Great! We bought a paid team account for a year and got this bug, super!

Why do you need a paid account if the key feature doesn’t work and breaks everything?

Hello everyone! 👋🏽

It seems to be working fine again, at least on the tests I’ve been doing this morning 👍

On another note, I know this is frustrating and it impacted a lot of businesses around the world (me included), but it also showed us that @anon21722796 really cares about its customers and their issues - and can act fast enough to not propagate this further.

I know this was bad and shouldn’t have happened, but… bugs happen, mistakes happen (we are all humans).

Figma team, keep up the great work, we can’t wait for the next great features you have prepared for us 🙌

Hi all. Seems to be good now. What worked for me:

1. Reverted the DS library to before the changes with the issues (fortunately there were not many changes to the DS in the past couple of days)


2. The DS library requested a publish since the changed components were reverted back


3. Did the publish, then did again the changes to the DS components. Published again.


4. Now on the affected files there are no more overrides.

Thanks @anon21722796 for dealing with this! We love you all!

Not sure if this is 100% confirmed to be resolved now, since the post mentioned above (“Please see the post below…”) has many replies of users where it’s still not working.

The big question: while this is being fixed, what do you recommend we tell all the users of our libraries? We have thousands of components across dozens of libraries used across hundreds of files. Should we advice everybody to NOT accept any library updates until further notice? Or to not work at all since they will have to revert to pre-Jan19 versions?

EDIT: I got the courage to re-publish the affected component sets to try on a few affected files and it seems that it’s retaining overrides! 👍 Now I have to redo the changes I wanted for those components and see if those changes don’t reset overrides again.

Hi folks, I might be stupid, but either the steps don’t work for me, or I did not understand the steps correctly.

I have two files: one with a Design library (containing all the master and variant components) and one with mockups built with instances from the master file.

I refreshed, reverted, and published new changes but they will still override the current ones. And it still happens with test components that I build a few hours ago. Is the issue really resolved for everybody? Is there a dumb step-by-step version of the fix that I can follow? 😅

I’m really in deep deep trouble here 😕

I also can confirm that it works fine for me now. However I had one component that I had created during the affected time span, which still did not work as expected. I made a new copy of this component and relinked all instances to the new one, works fine now.

So basically for the libraries to work again all components have to be in a state either before the bug appeared or after it got fixed.

Hope everybody will be able to restore lost data, and thanks to the @anon21722796 team!

NOT fixed yet. Reloaded figma, but overrides are still lost when accepting library updates.

Not fixed for me, I kept having major library issues all morning…

Not fixed, and getting anxious already. We have clients, ongoing projects that get damaged by this bug at this moment…

Thanks for the details Vasil.

@anon21722796 pls help with this bug, because we are pausing our work time. It is really a big problem! can you give us feedback when or if this is going to be resolved or do I need to detach all my instances and stop working with a library?

Okay I discovered something that might be useful to some !

If you update the library in the same design file where you designed your screens, the overrides stay as they are, no change.

But If you update the library in a file that it’s not where you originally designed the screens, ( maybe where you share them with the dev team ), the overrides are lost.

At least this is what I discovered in my case, I also lost days of work because of this.

but Omar this wasn’t the case until yesterday.

It is good practice to keep a separate library from the project file. I maintain a library that until yesterday was able to update without resetting all my designs, now if I change a style only, my designs revert to the original variant content.

Oh yes you’re right, I spent yesterday and today fixing everything manually, Now I just tested it and It’s all fixed for me no matter what changes I make and where.

Try traditional solutions like restarting the app, checking for updates … etc

Thanks for the comment, Vasily. But it did not help me, for example.

Hey @Raluca - if you haven’t already, please reach out to support and we’ll work with you to help you fix things now. The underlying issue has been fixed, but impacted files still need to be cleaned up. We have more tooling in the works that should help to streamline this process for those of you that are still feeling stuck, but we’re happy to help you manually in the meantime.