Skip to main content
Jackson K
Jackson K
New Member
July 1, 2025
Solved

Prototypes with Video Trigger Not Advancing Screens

  • July 1, 2025
  • 4 replies
  • 383 views

I have multiple prototypes that include a trigger that allows them to advance to the next screen. [When video ends > Navigate to] Some screens get stuck and don’t advance. It’s happening on old prototypes that used to work seamlessly and new prototypes and it happens intermittently. I’ve tried restarting my computer, clearing the cache and other troubleshooting tips from Figma community forums; however, I can’t find anyone that is having the same issue and nothing has helped. Sometimes, I can restart the prototype and all screens will advance as expected. But this doesn’t always work. 

This topic has been closed for replies.
Best answer by Jackson K

Tom, 

  1. Desktop App (haven’t checked in the browser)
  2. Yes, using latest version
  3. Components are copied from the same source (this helped)

I was able to find separate issues in the old prototypes and newer ones.

In the old prototypes, the component that holds the trigger to advance to the next screen was updated and somehow the trigger was removed on SOME screens. Creating a main component for each prototype file so that updates don’t trickle down resolved this issue. 

In the new prototypes, selecting ‘Reset video state’ in the interaction seemed to stop the intermittent pausing that was happening. I’ve tested multiple times and it hasn’t paused once. I don’t quite understand this fix so I’m going to keep an eye on it. 

Thanks for your help.

4 replies

Tom Reem
Figmate
Tom Reem
Figmate
July 1, 2025

Hey ​@Jackson K — thanks for flagging this, and I’m sorry to hear you’re running into this issue. Really appreciate you taking the time to troubleshoot so far. You definitely shouldn’t have to restart the app repeatedly just to get things working.

 

You may have already tried some of these steps, but to help us narrow things down a bit more, can you confirm the following?

  1. Are you seeing this issue in the Figma Desktop App, browser, or both?
  2. If using the Figma Desktop App, are you running the latest version (125.5.6)?
  3. For the new prototypes where the video trigger isn’t advancing — are those components copied from the same source, or do they come from the same library? If they were built separately but all show the same issue, that may help us isolate what’s going on.

 

I’d also love to loop in our Technical Quality team to take a closer look. When you have a moment, please fill out this secure form and include:

  • a link to the affected file and prototype
  • edit access granted to support-share@figma.com
  • a screenshot of the prototype settings for the component where the “Navigate to” action is misbehaving
  • a short screen recording of the issue in action (if possible)

 

Thanks again for bringing this to our attention — happy to help get things sorted. 💯

    Jackson K
    Jackson KAuthorAnswer
    New Member
    July 8, 2025

    Tom, 

    1. Desktop App (haven’t checked in the browser)
    2. Yes, using latest version
    3. Components are copied from the same source (this helped)

    I was able to find separate issues in the old prototypes and newer ones.

    In the old prototypes, the component that holds the trigger to advance to the next screen was updated and somehow the trigger was removed on SOME screens. Creating a main component for each prototype file so that updates don’t trickle down resolved this issue. 

    In the new prototypes, selecting ‘Reset video state’ in the interaction seemed to stop the intermittent pausing that was happening. I’ve tested multiple times and it hasn’t paused once. I don’t quite understand this fix so I’m going to keep an eye on it. 

    Thanks for your help.

      Tom Reem
      Figmate
      Tom Reem
      Figmate
      July 14, 2025

      Hi ​@Jackson K — that’s great to hear! 

      Appreciate you taking the time to revisit the components, and I’m glad that helped get things working more predictably.

      We definitely want to help keep performance as consistent as possible — and I understand how things can sometimes pop back up. If anything starts acting up again, don’t hesitate to reach out. We’re always happy to take a deeper look at the file if needed.

      I’m going to mark your last reply as the best answer so others with similar questions can easily spot the solution. Keep us posted with how it’s going. 🙏🏻

      Jackson K
      Jackson KAuthor
      New Member
      September 24, 2025

      Hi ​@Tom Reem, 

       

      Unfortunately, the issue has persisted. I completed the steps in the Technical Quality form. Let me know if more is needed. Thanks.

      Terms & ConditionsAccessibility statement