Skip to main content
Joao_Costa20
July 11, 2023
Solved

🚨 Variables: Deleted collections and modes don't disappear

  • July 11, 2023
  • 63 replies
  • 8764 views

When Variables was released I created some collections for testing. Since then I settled on a final version but the old deleted collections still appear in the page/layer selection on the right panel. The same is happening to deleted modes.

    This topic has been closed for replies.
    Best answer by djv

    Hey All, sorry for the continued frustration!

    As already mentioned above, our team needs your specific files where this is occurring to allow them to repro and work on the fix.

    If you have’t already, you can submit a bug report to our support team directly via the form here: https://help.figma.com/hc/en-us/requests/new?ticket_form_id=360001744374

    Be sure to use your Figma account email, include a link to the file(s) where this is occurring, and share edit access with support-share@figma.com.

    63 replies

    Show previous replies
    Neto_Ana
    August 30, 2023

    We are having similar issues. Please fix this.

    Jens_Brandt
    Jens_Brandt
    September 1, 2023

    I’m also having this problem, and especially in the combination with my shared library and local variables. So, please fix this asap, thx.

    Francis_Provencher_Leduc
    Francis_Provencher_Leduc
    September 25, 2023

    Any head-ups on this ?
    This is an issue !
    Even by creating a new theme (over the deleted ‘spot’), it still show unavailable.

    Jelle_de_Graaf
    Jelle_de_Graaf
    September 26, 2023

    I have the same issue. I already reached out to the Figma support team. The issue was not resolved. I would like to hear something from Figma within this threat. For us it’s a serious issue, now we’re building a theming layer. Please fix this!

      Francis_Provencher_Leduc
      Francis_Provencher_Leduc
      September 29, 2023

      With the limited variable mode of 4.
      I need 2, that fine.
      But, with that bug, For some collection, I can’t do my work anymore, as 3 spot a taken by those deleted.

      Nate_G
      Nate_G
      Power Member
      September 29, 2023

      I had a similar issue and found that I was still referencing some variables & modes from a deleted collection. Once I broke or re-assigned all those connections, the deleted collection and modes finally went away.

      Screenshot 2023-09-29 at 2.33.46 PM

      Nate G
      jjcm
      Figmate
      jjcm
      Figmate
      October 6, 2023

      Hey all, PM for variables here. This is caused by variables still being present in the file from the deleted collections. One easy way to fix this is to detach deleted variables in the file. There’s a quick command for this as well:
      image
      You will have to run this on every page of your file. If you still see this persisting, close the file for a couple minutes so the garbage collection routine can run. If you see it still persisting beyond that, send me a ping at jake@figma.com so I can have the team look into it.

        Rob_Winters
        Rob_Winters
        New Participant
        October 12, 2023

        Detaching deleted variables didn’t work for me. I even deleted all frames from the file as a test, but still the deleted collection appear.

          Joao_Costa20Author
          October 12, 2023


          As you can see in the video. I’m not using any deleted variables in both libraries.
          The deleted variable collection(Latitude components) still appears and some modes on the active collection(Latitude foundation) are grayed out and disabled.

            Andrea_R
            Andrea_R
            New Participant
            October 19, 2023

            I removed/detached all variables, use every command and solution suggested in this whole forum or elsewhere but it didn’t work for me.
            I even copied the library components into a new document, one component after the other. Eventually even detached the cleared components before copying into the new document. The deleted collections still appear again.

              Show more replies
              Terms & ConditionsAccessibility statement