Figma branches are repeatedly failing in ways that block design system work and compromise the reliability of library updates.
Key issues observed:
-
Library updates continuously reappear
When creating a branch, Figma shows “updates to the library” that have already been resolved. These same updates reappear over and over, even after being accepted in previous branches. -
Merged work does not appear in the main file
After merging a branch, the new work doesn’t show up in the canvas—even though it does exist. Using Cmd + Y reveals the updated content, but it remains invisible in the main file. -
Forcing us to delete branches and redo work
Because the merged content won’t appear, we’re forced to delete the branch entirely and re-create the work from scratch. No amount of refreshing, reloading, or republishing makes the work visible.
Impact on Design System Workflow:
As a design system designer managing multi-file component libraries, branching is a core part of our workflow. These bugs make it nearly impossible to deliver updates reliably. They create confusion, duplicate effort, and a high risk of publishing incomplete or incorrect component changes.
Requesting investigation into:
-
Why library updates reappear when creating new branches
-
Why merged content becomes “invisible” but still technically exists
-
Whether versioning or branching logic is corrupting the file
-
Any known issues with branching on large multi-page component libraries
This is currently a significant blocker for completing and shipping design system updates.
