figma weave generating broken component instances

When using Figma Weave to generate layouts that pull from design systems, you may encounter broken component instances, missing variant properties, or auto-detached components marked with warning icons. This occurs when the AI generator loses access to the underlying design library or fails to resolve component variants correctly during assembly.

Quick checks

Before rebuilding your components, check these requirements:

• Verify library access: Make sure the target design system library is published and toggled ON in your current file's Assets panel.
• Check server responsiveness: If design libraries fail to sync entirely, confirm if API services are running via our Figma Weave server status guide.
• Inspect variant names: Ensure your design system components do not use duplicate property names or special characters that confuse the generator.

1. Publish outstanding library updates

If you modified master components recently, published updates might be pending. Weave relies on published library indexes. Click the Assets panel, publish all pending changes, and re-run your generation.

1. Re-link unattached instances manually

If Weave creates ghost instances with missing main component links, select the affected frame, open the right sidebar, and click Restore Main Component or re-assign the instance using the Instance Swap menu.

1. Reduce design system scope in prompt settings

Giving Weave access to massive, unorganized library files with thousands of components can cause variant lookup timeouts. Limit active file libraries to only the primary UI kit needed for your design sprint.

1. Force a cache refresh and re-generate

Stale design token caches in Figma can cause Weave to attempt binding to deleted variant IDs. Reload your tab or restart the Figma desktop application, then follow our steps on resolving stuck Figma Weave generation processing.

Still stuck?

If component instances continue to detach upon generation, test the same prompt using raw Figma native shapes rather than a custom library. If standard shapes work, inspect your design system for circular component dependencies or unmapped nested variants.