Skip to main content
Question

Libraries not updating after last update

  • August 3, 2026
  • 7 replies
  • 63 views

hvw83

Since August 3 my Libraries won’t update any more. Even creating a new one with just one component refuses to publish. I restarted Figma, reset the cache, tried publishing via the browser, nothing works. When clicking the publish button it says, “assembling components, styles and variables”, the modal closes, but nothing happens after that (normally I would see a progress bar and things get published).

 



 

 

7 replies

Celine_
Figmate
  • Community Support
  • August 3, 2026

Hey there, Celine from the Community Support team at Figma here.Thanks for sharing the details and the screenshot!
The troubleshooting you've already done—restarting Figma, resetting the cache, trying in the browser, and testing with a brand-new library—are all great steps and help narrow down the issue.

Based on what you've described, the publish flow starts ("Assembling components, styles and variables") but doesn't proceed to the publishing step. Since the same behavior occurs with a brand-new library containing a single component, it doesn't appear to be related to a specific component in your library.

Before submitting a bug report, could you also try the following:

  • Make a small change to the library (for example, update a variable description) and try publishing again.
  • Check whether the file is using any missing local fonts.
  • If you haven't already, try publishing from the desktop app.

If the issue persists after these steps, please submit a bug report. Go to the Support Hub / Type “Report a bug, Contact agent” / Click Start a chat / Select Enter and follow the prompts. Our support team can take a closer look at it.

When you submit your report, it would be helpful to include:

  • A link to the library file and grant "Can View" access with support-share@figma.com. This allows us to reproduce the issue and investigate.
  • The affected team/workspace.
  • A screen recording of the full publish flow (if possible).
  • Your Figma desktop app version and browser version.
  • The steps you have already tried

Thank you!


hvw83
  • Author
  • New Member
  • August 5, 2026

It started working again shortly after posting my first message, but later I experienced the same issue once more, except this time I got a popover telling me something about having multiple sessions. Through the popover, I was able to see all sessions, of which there were four, all with the same IP address and location. I closed the sessions and created a passkey (all through the popover), after which I haven't experienced any of the problems mentioned. Just sharing this here for anyone who might stumble upon the same issue. I am not sure if the sessions thing is a new feature, but it would be great if the session model would be triggered every time an action is blocked. Now there is no feedback on what is happening and why things don’t come through. Anyway, thanks for the quick and detailed answer.


Celine_
Figmate
  • Community Support
  • August 5, 2026

Hey again, thanks for coming back to share this, it's really helpful for anyone else who might run into something similar!

This does seem unexpected, and I can't confirm whether the sessions prompt was related to the publishing issue. I appreciate you sharing your feedback about the lack of indication when an action is blocked.

If it happens again, please reach out to our Support team and, if possible, include a screenshot of the sessions prompt to help with the investigation. Thanks again for following up!


hvw83
  • Author
  • New Member
  • August 12, 2026

@Celine_ The problem keeps coming back. See the attached screen recording. Today the problem started happening again after I used the “Reset Figma and Restart.” I am not sure if those things are related because it doesn’t “trigger” the bug all the time. If I wait for some time, the publishing starts working again, but this does take at least an hour, it seems. The recording is from a totally new library file with one newly created component, but the bug happens in all of my libraries. I am not sure if it’s useful, but here is also a link to the file (with read permissions).

 

 


Celine_
Figmate
  • Community Support
  • August 12, 2026

Hey again, thanks for coming back with the screen recording and file link!

Since the issue has returned and you're able to reproduce it across multiple libraries, including a brand-new library with a single component, I'd like our team to take a closer look rather than have you continue troubleshooting this here as they are best equipped to take a closer look at it.

I've gone ahead and created a support ticket on your behalf and included the context you've shared in this thread. You have received an email where you can continue directly with our support team. For reference, your case number is #2067540, sent to your email address: hxxxs.vxxxxn.wxxxk@axxxx.n

Please keep the affected file available with Can View access for support-share@figma.com, as this will help the team reproduce and investigate the publishing behavior. Thanks again for taking the time to document this so thoroughly!


hvw83
  • Author
  • New Member
  • August 12, 2026

@Celine_ Sorry to spam you, but I just got the following popover:


This modal is occasionally triggered after the “Reset Figma and Restart” command.

When going into the session overview, I see this (blurred my IP, but there are all the same numbers):
 


To me, it looks like the session thing is the reason I can’t publish my libraries, since they always seem to occur together. 


Celine_
Figmate
  • Community Support
  • August 12, 2026

Thanks for sharing the screenshot! I’ve also added these details to your existing support case, as our support team is best equipped to investigate account-specific issues like this.

Please share any additional information directly through your support case so everything stays in one secure place and our team has all the context needed for the investigation. Thanks!

Update: The support agent has replied to you with the next steps, and is waiting for your response. Please check your inbox when possible, thank you!