Hi @Jake_Round, Thanks for getting in touch about this issue, I can understand how frustrating this must be for you.

From what I’ve gathered internally, this may be happening because the page-level UI is pulling from all the variables used in the file. It might possible that somewhere in this file, outdated variables are being used.

Could you please check if any instances in the file are using these outdated variables? If you find any, could you try going to the library where the main components are included, accept all updates, republish them, and then accept the updates in the file with this conflict mode issue to see the difference?

However, I note that we currently have a limitation. If there are locally deleted components that use outdated variables, accepting updates might not resolve the issue. Please know our engineers are actively working on this!

Hope this information helps a bit. Let me know if I misunderstood anything.

Also, we always welcome any insights or suggestions from our community, if you have one please jump in!

If none of these helps, I suggest you to reach out our support team directly here: https://help.figma.com/hc/en-us/requests/new

When you contact our support team, please provide the following:

1. Use your Figma account’s email address.


2. Share the direct link of the file with mode issue, and please add support-share@figma.com as an Editor to those files (this won’t impact your billing).


3. Let our support team know what troubleshooting steps you’ve already tried.

Thank you for your support!

Thanks for your response @Junko3

I’m going to assume it is the latter, I’m really struggling to resolve the issue, i’ve double and triple checked there are no legacy styles applied. I have raised a support ticket in the meantime.

I wonder if there is a solution, i would really like to try and avoid rebuilding both files as that seems like a waste of time.

Thanks

I’m having the same problem. 😡 I can’t understand how such a simple question wastes our time. While it could be solved with a very simple plug-in and bug-fix, Figma leaves us with the problem. 😭

Hi there, Thank you for reaching out and sharing your feedback with us. I completely understand your frustration.

I wanted to share this article Modes for variables - Mode conflicts. It offers some suggestions on how to clear old variables from your file that may be causing conflicts.

If you’ve tried those suggestions and are still experiencing issues, I recommend reaching out to our support team directly for further assistance. Please refer to the instructions provided in the second post quoted below.

Thank you for your understanding!

Hi, same problem here,

I have a file with no variables from other libraries. Only local variables. And i have a conflict on a mode that I just created.

i tried to reassign all my variables, in order to be sure that the last version is assigned, but my problem is still here. The error message tells me to republish the library, but there is no library ! only a file with local variables.

I need help, it affects all the file connected to this first library (My components, my products, my illustrations…)

Hi @Thibault_Serre1, Thank you for getting in touch about this.

In order to assist you, I have gone ahead and created a support ticket on your behalf. The ticket number is #1071884. Kindly provide the details requested in the ticket by responding to it directly.

Thank you for your understanding and cooperation in this matter.

The article only addresses mode conflicts in external libraries. It doesn’t address local mode conflicts, which is the subject of this discussion.

I have the same issue. I cannot even select my local variables even though they were set up in this file. Instead, I’m restricted to variable sets from another file.

The article doesn’t say much to be honest.

Also the conflict error isn’t really specific either, especially when you have to maintain 1.000+ components in a multi-brand design system. Might there be a solution similar to “branch conflicts” if a variable becomes outdated in a file because it was renamed, deleted and adjusted?

Hello there, Thank you for getting in touch. Sorry to hear that the Mode conflicts document didn’t address the issue you’re facing.

While it may not be exactly like Resolve conflicts for branch but you can try “Detach deleted variables” command. You can access that command from action menu in the tool bar. Please refer to this comment for how to use the command:

If the issue continues to persist, as each mode conflict problem can differ depending on the case, I understand it may be a bit inconvenient, but I suggest reaching out to our support team directly, as I previously mentioned. They can offer personalized assistance to help address this matter.

We truly value your feedback and understanding.