Library component updates stuck in update loop with “Preview unavailable” and incorrect instance counts

We are experiencing an issue with published components from our Tria Design System library in a consuming Figma file (Tria Mobile App (Current)).

Certain library updates cannot be successfully applied. When we accept the update, Figma appears to process it, but the same update immediately reappears. In Review updates, both the current and updated previews show “Preview unavailable.”

There are currently three affected components:

• Utility Support — simple icon component. This issue has persisted for approximately one week. Review Updates reports 25 instances.
• Info — simple icon component. This issue has also persisted for approximately one week and reports 2 instances.
• Text Field Single Line — began exhibiting the same behavior today, immediately after I rebuilt several component properties and published a relatively large update. It reports 2 instances.

Utility Support investigation

This component is particularly easy to reproduce/debug because it is extremely simple: it contains only a vector shape and has no variants, component properties, exposed nested properties, or other complex configuration.

I have already tried:

• Repair Component Connections
• Rebuild Connected Instances
• Updating individual instances
• Update All
• Republishing the library
• Locating and manually replacing known instances

None of these resolves the issue.

There also appears to be a discrepancy between Figma’s library-update state and the actual document.

With “Show updates for all pages” disabled, Figma reports “1 of 25 instances” of Utility Support on the current page. However, searching that same page for Utility Support finds only 2 actual instances. Those two instances can be selected and navigated to normally.

Across the document, Figma’s search also does not appear to account for the 25 instances that Review Updates claims require updating.

As a test, I recreated Utility Support as a completely new component with a new component identity and published it. The newly created component works correctly and does not enter the update loop.

This makes me suspect there may be stale/orphaned instance references or component metadata associated with the original published component.

Text Field Single Line

The text-field issue may have a different trigger.

Unlike the two icons, which have been affected for approximately a week, Text Field Single Line only started failing immediately after a substantial component-property restructuring and library publication today.

It now exhibits the same consumer-side symptoms:

• Preview unavailable
• Update appears to apply
• Update immediately returns
• Component remains listed under library updates

I have not recreated or replaced this component because it is a heavily used design-system component and I would like to preserve the current state for investigation.

Expected behavior

After accepting a published library update, the affected instances should update and the update should disappear from the pending library updates.

Actual behavior

The update appears to process but immediately returns. Review Updates cannot generate previews for the affected instances, and in at least the Utility Support case, the number of instances reported by Review Updates does not correspond to the instances discoverable through Figma’s document search.

Could you please investigate the underlying component IDs / instance references / library update metadata for these affected components? In particular, it would be useful to understand what the 25 Utility Support instance references in Review Updates correspond to, since they do not appear to be discoverable in the document.

I can provide edit/view links to both the Tria Design System library file and the Tria Mobile App (Current) consuming file, as well as screenshots/video demonstrating the issue.

Environment
Figma Desktop for macOS
Issue reproduced in: Tria Mobile App (Current)
Library: Tria Design System
Date observed: September 20, 2026


Link:
 

Update:
 

I performed a full document-graph audit using Figma Agent, hydrating all 13 pages and 10,000+ instance nodes.

The Agent successfully identified the exact 25-instance cohort reported by Review Updates as:

Home Topbar → Buttons Icon → Support

All 25 instances successfully resolve to Support component ID 1832:254367, key c9631ff30b5d53dea47c57df0c0e9314fd338870.

The audit found no unresolved component references, stale component-property mappings, missing nodes, invalid instance swaps, missing variables/styles, structural mismatches, or broken override targets.

All instances use the current valid Buttons Icon property Icon#188:32, and the Support swap resolves correctly.

Critically, other Support instances outside the 25-instance cohort have identical observable state but are not included in the pending update.

As an additional diagnostic, I completely removed the relevant Support dependency from Home Topbar and published the library. Review Updates nevertheless continued to report the same 25-instance pending update. I subsequently restored it because it is part of the intended design.

The Figma Agent’s conclusion is that there is no document-model-visible difference explaining the pending update. The remaining suspected state is library revision/update bookkeeping that is not exposed through the document model.