Recently I have major issues with component instances not being rendered correctly.
Every other component instance is rendered incorrectly upon opening the file. To fix the problem I have to click into every instance, which seems to correctify it but is a major painpoint since I have hundreds or thousends of instances all over different files. This means I have no idea if the handoff to the programmer is actually correct since I don’t know which instances are incorrect or if they are rendered properly or not on the different devices.
6 Likes
Please also submit a bug report.
2 Likes
I’ve had the same issue and it’s very frustrating.
Sorry, haven’t seen your response.
I’ve reached out through the in-app bug reporting interface and they’ve suggested the same thing to fix the issue.
It worked perfectly well for me. The issue returns every once in a while, but now at least I don’t have to fix all the errors manually.
Thanks for your response!
1 Like
My team has been having the same issue, thank you for sharing.
Had the same issue, rendering complex prototypes useless because nested components would not display correctly. Double-clicking on individual instances temporarily “fixed” the issue one by one, but this method would be untenable for hundreds of instances.
Thank you for suggesting Regenerate all instances (slow) from the Quick Actions panel. It seems to have fixed all instances, but I am still verifying that this step has carried over manual overrides that were set during fast iterations in the layout process.
1 Like
I have the same problem. This is a major flaw that needs to be fixed if we are to trust Figma. Otherwise, the use of components is useless if we can’t trust that what developers are looking at is what we designed.
Chiming in here; happens to me too and is very annoying 
Sad to see this issue has been occurring so long already…
We have a design system and multiple project files, but one of the instances isn’t rendering correctly in a particular file. It’s really weird and frustrating. I can’t create a new file because there are too many flows and pages inside it, and I need to use this one primary variant on almost every page. The strange thing is, everything works well locally and in other design files, but for some reason, it’s not rendering properly in this specific file.
My team has the same issue. Seems to happen when using text variables to automatically switch a property using modes.
Please fix it, it’s very frustrating 
My team have faced the same issue. How can we fix it? according to replies I got that if we use Regenerate all instances (slow) all of the instances will be set to default main component. right?
Hi there,
If the instances are not rendered correctly, we suggest “Regenerate all instances (slow)”. It is like refreshing/updating as if you were clicking into a layer, but does so automatically on all instances in the file. Sometimes double clicking can fix this kind of issue. So, could you give it a try?
Also, please submit a bug report detailing the steps that led to this issue so our team can investigate it. You can do so by following the link:
Thanks,
Toku
I have the same issues as yours. Did the “Regenerate all instances” action preserve manual overrides?