Hey i hope anyone has some tips for me.I’ve been working with the windows app since january and experienced cache issues when making changes in the library and publishing to working files.Recently i split the components library up into 2 files, 1 for variables and 1 for components. We are running a multibrand design system and it was starting to get unweildy with just one library file. All ok there.So the structure is:variable library components library pulling in variables consuming working file linking to both libraries All of our components are built using atoms and nesting. But even just placing a button in the consuming file doesnt show eg the updated font colour.Now our freelancer who uses a mac has also started experiencing caching issues in the working files. We regularly delete cache. But changes do not show. Its starting to get a real problem 😭😭😭😭

Hi @KatK,I understand that updates published from your libraries are not reflecting in your working files.To cover the basics first, please confirm whether you are accepting the library updates in your working files after publishing changes. The Libraries icon should display a blue badge when updates are available.If you've already accepted the updates but the changes are still not reflecting, you might want to try the repair tool:Open the file where the instance doesn't look as expectedSelect the instance → Open "Actions" in the toolbar → Select "Repair component connections"Refresh the file and try adding a new instanceIf the issue persists after trying the above, I'd recommend submitting a bug report so our team can investigate further. Here's how:Go to the Support Hub → Type "Report a bug" → Click "Start a chat"Please include the following:Direct URLs of the files where the instance doesn't look as expected, and the library the component is fromShare view access to the affected files with support-share@figma.com (our official Support account — you won't be billed for this access)Any screenshots or video recordings of the issueTroubleshooting steps you've already triedWith this information, our team will be able to take a closer look more efficiently.Thanks!

Question

Cache & lagging issues with libraries

Forum|Forum|21 days ago
May 26, 2026
3 replies
34 views

KatK
New Member

Hey i hope anyone has some tips for me.

I’ve been working with the windows app since january and experienced cache issues when making changes in the library and publishing to working files.

Recently i split the components library up into 2 files, 1 for variables and 1 for components. We are running a multibrand design system and it was starting to get unweildy with just one library file. All ok there.

So the structure is:

variable library
components library pulling in variables
consuming working file linking to both libraries

All of our components are built using atoms and nesting. But even just placing a button in the consuming file doesnt show eg the updated font colour.

Now our freelancer who uses a mac has also started experiencing caching issues in the working files. We regularly delete cache. But changes do not show. Its starting to get a real problem 😭😭😭😭

J

Junko3
Figmate
Forum|Forum|20 days ago
May 27, 2026

Hi @KatK ,

I understand that updates published from your libraries are not reflecting in your working files.

To cover the basics first, please confirm whether you are accepting the library updates in your working files after publishing changes. The Libraries icon should display a blue badge when updates are available.

If you've already accepted the updates but the changes are still not reflecting, you might want to try the repair tool:

Open the file where the instance doesn't look as expected
Select the instance → Open "Actions" in the toolbar → Select "Repair component connections"
Refresh the file and try adding a new instance

If the issue persists after trying the above, I'd recommend submitting a bug report so our team can investigate further. Here's how:
Go to the Support Hub → Type "Report a bug" → Click "Start a chat"

Please include the following:

Direct URLs of the files where the instance doesn't look as expected, and the library the component is from
Share view access to the affected files with support-share@figma.com (our official Support account — you won't be billed for this access)
Any screenshots or video recordings of the issue
Troubleshooting steps you've already tried

With this information, our team will be able to take a closer look more efficiently.

Thanks!