Skip to main content

Instance of a deleted variant doesn't receive updates or indication that the component has been deleted.

  • June 4, 2026
  • 8 replies
  • 89 views
JR_Rowland

This happens to us frequently when architecting a library file:

  1. A concept file has several instances of a component - that component has many variants and all of them are placed in the concept file.
  2. Now we delete some of the variants in the library file, and make various changes to the other variants. The library file is republished.
  3. After updating components (sometimes on all pages, sometimes just the current page), the variants with just changes seem to update well. However the instances of variants that were deleted in the library file just sit there - no update prompts, no “main component was deleted” type messages. We can even change properties of these instances. Its as if the concept file is hanging on to a memory of the library file and not flagging an issue.

What we’d expect: An indication that these components are now effectively detached so we can choose to update them to a variant to still exists.

What we’d love: A guided flow similar to the “missing fonts” flow, where substitutions are suggested and committed.

    8 replies

    Jaycee Lewis
    Figmate

    Hey ​@JR_Rowland 👋 Thanks for your post 🙌

    To make sure I understand the root issue, can you grab a short screen recording? One that walks through the republish, the "update components" action, and the instance sitting there afterward unflagged. Seeing the Layers panel state on that instance (the diamond icon) at the end would tell us a lot.

    A couple of quick things to confirm while you're at it:

    • When you delete the variants, are you deleting the *whole component set* (the full variant group), or just *one or more variants from a set that still publishes*? Those can behave differently, and the distinction will shape how we report it.
    • After the republish, do the affected instances still show as instances in the Layers panel, or have they changed state at all?

    On the substitution flow you described — that's a great fit for our Suggest a feature board, where others can add their votes: https://forum.figma.com/suggest-a-feature-11 

    Thanks! — Jaycee

      JR_Rowland
      • JR_Rowland
      • Author
      • New Participant
      • June 5, 2026

      ​@Jaycee Lewis I attached a screen recording here. Answers to your questions: 

      • When you delete the variants, are you deleting the *whole component set* (the full variant group), or just *one or more variants from a set that still publishes*? Those can behave differently, and the distinction will shape how we report it.

      Deleting just one or more variants from a set that still publishes.

      • After the republish, do the affected instances still show as instances in the Layers panel, or have they changed state at all?

      They still show as instances in the Layers panel.

      Thanks!

       

      JR_Rowland
      • JR_Rowland
      • Author
      • New Participant
      • June 5, 2026

      One last note is that when the main component is within the same, Figma seems able to identify when the a variant has been deleted. The issue I’m describing seems to only apply to published library files where the main component is not in the same file as the instance. (screenshot attached shows the message Figma provides when a variant is “missing”)

       

      Jaycee Lewis
      Figmate

      Hey, ​@JR_Rowland 👋 I want to check in. Is this still occurring for you? — Jaycee

      Emilyer
      • Emilyer
      • New Member
      • June 29, 2026

      This happens to us frequently when architecting a library file:

      1. A concept file has several instances of a component - that component has many variants and all of them are placed in the concept file.
      2. Now we delete some of the variants in the library file, and make various changes to the other variants. The library file is republished.
      3. After updating components (sometimes on all pages, sometimes just the current page), the variants with just changes seem to update well. However the instances of variants that were deleted in the library file just sit there - no update prompts, no “main component was deleted” type messages. We can even change properties of these instances. Its as if the concept file is hanging on to a memory of Yacin tv apk of the library file and not flagging an issue.

      What we’d expect: An indication that these components are now effectively detached so we can choose to update them to a variant to still exists.

      What we’d love: A guided flow similar to the “missing fonts” flow, where substitutions are suggested and committed.

      An issue where an instance of a deleted variant does not receive updates or any indication that the original component has been removed can lead to confusion and inconsistencies in a design system or development workflow.

        JR_Rowland
        • JR_Rowland
        • Author
        • New Participant
        • July 6, 2026

        Hey, ​@JR_Rowland 👋 I want to check in. Is this still occurring for you? — Jaycee

        yep - this still happens. Its a type of drift that is very difficult to catch in QC.

        Jaycee Lewis
        Figmate

        Thanks ​@JR_Rowland I’ll get a support ticket open for us. You’ll see a request in there to add the following so support can reproduce and troubleshoot:

        • A link to the file with view-only access
        • A full-screen recording that isn't zoomed in (so we can see the whole context)
        • Relevant screenshots
        • Any other details that might help

        I’ll loop back and add the ticket ID and email subject line back here so you can locate in your email inbox. Talk soon! — Jaycee 

        Jaycee Lewis
        Figmate

        Hi, ​@JR_Rowland Your ticket ID is 2000521 and the subject line is Instances of deleted library variants aren't flagged as orphaned or offered a resolution path. Thanks again! — Jaycee

        Terms & ConditionsAccessibility statement