@Alex_Gough Can you reach out directly to support@figma.com. We’ll ideally need to take a look at the files to see why this might still be happening.

If you can reach out and share both the library file and instances file with us, with edit access (please give edit access to support-share@figma.com)

Also if you could point us to the exact instance that’s experiencing the problem and the exact overrides that are lost, that would be super helpful.

Thanks

Can confirm that reverting all files to January 18 fixed it for me.

Hey Josh! Thanks for the reply. Unfortunately I’m unable to share files/libraries due to privacy policy of the company. Is there any diagnostic data I can capture and provide from the app?

Is the only current solution to revert to Jan 18 and redo work from there?

Unfortunately we’ll need to take a look at the actual files and components to see what might be happening here. It looks like your an Org user so you should be protected by either your MNDA or your MSA, meaning you should be fine to share the file with us, as our data / intellectual property protection measures will be outlined there. If you have further questions though let me know and we can see about connecting with your account manager here.

This is seriously unfortunate, we may have lost the last 2 days of work here. We’ve been creating a new library and testing it in files, all the tests are being overridden as we push. I can’t revert back to the 18th as I’ll literally have nothing to show for the effort we’ve put in.

Vasil, You were able to accept updates from your library and the overrides remained intact? Sorry, if I’m asking what you already answered, I just wanted to make sure I understood fully before reverted my file to the 18th.

The fix does not seem to work for my teams either here. I am not sure if it is because we have Branches of the main library open or if because other people simply have the disgn library file open. Either way updating from the Library file is overwriting text changes in instances in our design files.

So we all lost work from about one workday.

Working with 20 people means a lost of 160 hours of work.

Would those people be freelancers and work for 80 euro

an hour it would be a total loss of 12.800 euro in total.

In one company.

Yap, shit just hit the fan …

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

We’ll need to take a closer look to diagnose what’s happening, so please also share those files to support-share@figma.com if possible! Linking to the exact instance would be a huge help to our team in diagnosing what’s happening here.

Thanks!

Ok, to clarify I think I misread the fix…

1. We need to revert our Library file to a version prior to Jan 19th - 2pm PST.


2. Then republish the Library

Once we have done that then updates from the Library should work, is that correct?

I had only reverted one of the design files

Reverting should only be necessary on the instance file. After that, you’ll need to:

1. refresh your tabs (or close/reopen the desktop app)


2. make a change to the Library file and publish it


3. go back to the instance file and accept the update

Happening on new files too, added some components, entered some overrides, made a change to the library and pushed, overrides reverted to pushed from library.

I have the issue since yesterday afternoon. And it blocks my work. What should I do?

(I already emailed support yesterday afternoon but no answer)

Backroll the library as mentioned above.

Reload all tabs or restart the app.

Update all instances.

Shit should be the same than before.

Redo all changes you made after the backroll again.

Update all instances.

Done.

Sounds easy, but its a lot of work. I started working at 8am. Its almost 1am again and I´m not done yet 😦

Major major Fkkkk up! And the fix/description does not work… This will take days to clean up…

I tried to restore my file to yesterday and it looked fine. but after I clicked done all the fields are wrong again. We have a team of developers working from this file and now everyone is delayed. I have added figma support to the file

We were able to resolve the issue following these simple steps. Hope this helps someone.

1. Close and re-open Figma.


2. Revert your design library (aka style guide) to a version saved on Jan 18th before 2pm.


3. Publish that library.


4. Update the library with any changes you made after 2pm on Jan 18th.


5. Publish those library updates.

You should be all set.

point 3. can take ages to rebuild 💃

Hi Anders! 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!

Sadly its been 5-6 hours since the “fix” was released and the problem has returned and nuked all hour work since it was “fixed”. It’s all ruined again. A days work by the team reset.

We’ve released an update which will prevent the issues in libraries published during the window of 2022-01-19T22:30:00Z til 2022-01-20T23:00:00Z from affecting insertions in newly created files. Existing files with impacted instances will still have to follow the previously noted steps to manually fix their state, however your instances and overrides will revert back to the way they were before the problematic update.

For those with significant updates made that would be lost, we’re working on a possible fix to preserve overrides made during the affected period. We’ll continue to update you as we work on this.

When will it be fixed?

1. Manually reverted to the previous version and then updated again


2. After updating, the same problem appeared again.

I have mistake the same here:

"I got an issue when updating components on a Design System file. After making some modifications, such as changing the font-weight from Regular to Black, then I publish that change. Next, I access the design file and apply that change. I feel frustrated when all the values I input before for those items are reset back to the original component.

For example, the component has Label > Value. And the instance of that component in the design file is Full Name > John Doe. After updating and applying, the instance is reset to Label > Value instead of keeping the input value Full Name > John Doe."

I have File 1 and File 2. (Due to many screens)

I normally publish File 1 library master and click update in File 2. (so I can use the same master)

In File 2, I edit the text of an input field (Master From File 1)

When I update that component in File 1 → publish again → Click Update in File 2.

Normally, the edited text will not be overridden. (Only color? size will be overridden?)

But this time, it overrides my text, change back the text to ‘Label’. Dunno why… (cry)

Hey @Josh This isn’t working for me either. Happy to share both the design system and its instance files.