I personally think this is a massive road block to using interactive components “interactively”. If you can’t have a select that switches between a default/active/interactive state in an overlay modal that when the modal closes the states reset to default then what’s the point.
For me this shows just how behind Figma is on the prototyping front compared to the complexity that ProtoPie and ProtoIO deliver.
i am finding myself in this very situation with multi-tier navigation. everything works as expected on the initial path, but when returning to the origin page, the specific secondary flyout menu used to first navigate is stuck in an open position, where I would like it to return to its original state. totally agree with the proposed solution of being able to set the origin back to its initial state upon navigating to a new frame.
having the same problem. I’d like to either ‘reset’ or choose a state the interactive component is in when going between frames (using same component). The current implementation requires re-creating a noodle of pages (as someone else just mentioned) making them useless.
Hi folks.
Excuse me for my english but I will try to explain.
The same problem - I have a “dropdown menu” component that looks like “hamburger” icon and a list of items that appears when user clicks on icon. Each item should lead to other frame. In other words, it is a simple navigation that is used on any website. And instances of this component are placed on different frames (website pages) at the top with “no scrolling”. So I click on hamburger-icon. List appears. And when I click on one of the menu items I should jump to another frame in its initial state - with collapsed menu. As it should be on websites. Ex: I have a list - home, about, gallery etc. Initially flow starts on “Home frame” with collapsed menu. Then I click on “About” item and jump to “About frame” which initial state is also with collapsed menu . Then I click again on hamburger-icon → menu opens → I choose “Home” and return to Home frame. This frame should be with collapsed menu. But it remains with opened menu from previous visit. Then I click again on “About”, jumps to “About page” and now it is also with opened menu.
I’ve tried to work around this issue by adding “Mouse leave” interaction (by the way, this is not exactly a workaround, because when you move mouse away from menu, it should really disappear) in hope that jumping on other frame will be concidered a mouse leaving. No effect. Apparently different instances of menu component placed on different frames and even named differently, count as one.
Also I’ve tried to combine “Touch up/down” and “Tap” interactions but unfortunately it doesn’t works properly.
I see that this problem has not been solved for a year.
It would be very cool if
Same problem.
I open a drop-down menu on a frame, click a link in it to a different frame, and then when I click a link back to the original frame the menu is stuck open from before.
Honestly, this (interactive components) is the main reason I was switching to Figma from Sketch + Invision - if I am back to creating a static frame for every state, then I might as well stick with Invision…
+1 from me.
There’s a frame in my prototype that when a user navigates to it, I want everything in its base/starting state, regardless of what they might have interacted with previously.
This problem still persists. it is sad I seems stuck, found a couple of workarounds but it doesn’t do it for me.
+1
a really needed feature
+1
Same issue. It would very very useful
+1 for me too.
I’m trying to make a fairly simple toast notification component, but it seems like its impossible as a standalone component.
A button opens the modal toast, but when its finished and I use the button again, it always ends up on the last interactive frame.
+1, very annoying having to always start my prototype flow from scratch to assure all interactive components are reset/back at the start.
+1 this issue keeps coming up for me as well
+1 for me too
+1 I am making flow for creating the object in 3 steps. Without resetting stepper component state I am stuck on last step every time after first testing
There is an even more annoying problem with the addition of component props: if you change the state of a prop in the instance, then in the prototype you press R it will jump to default variant props, and there is no way to avoid this. 
You can fix that by reloading the prototype or by modifying the prop in the editor (which means that you have to share the prototype on a very controlled environment).
This is a big miss. I’d suggest more interaction between variants and outside elements. For example, on button click change component X variant state to… In addition, include an “on frame load” interaction that can also set the variant state. Currently there is the “after delay” interaction that works if you set the delay to 0 or a tiny fraction of a second (if 0 isn’t allowed). But I think the key here is allowing change of variant state from elements outside of the variant. That would make my life much easier.
No news from the team on this one? Really needing this 
Running into the same issue…makes it waaaaay hard to use interactive components when there isn’t a way to ‘refresh’ their state or have a reference marker tied to a frame.
Same problem… Where is the answer? I used to use Proto.io and they just gave you multiple actions upon click… you could navigate to another frame and change the state of the navigation component. Why is this tens of billions of dollars company not able to do something so remedial?
