Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Troubleshooting a Figma prototype

If you encounter an error while adding a Figma prototype to your mission, follow the advice below to troubleshoot.

Local files can't be added to a mission

This error is displayed if the website you attempt to enter belongs to a local file on your own computer. Local files cannot be accessed by participants, so they are not supported.

Instead, use a public Figma prototype link or a live website, as these can be shared with your participants during your study.

Shortened prototype link

If you receive a shortened prototype link error, the URL included in the task question is a shortened version of the original prototype URL and will not work correctly. For example, this may happen if the URL is copied from a Slack message.

To resolve this error, grab the prototype link directly from Figma and paste in Dscout. Learn more about how to get the correct share link in Prepare a Figma file for a Dscout study.

Missing starting point

When testing a Figma prototype, the prototype must have a starting point. If a starting point is not set, the prototype will result in an error.

To resolve this error, add a flow starting point to the prototype. Once added, grab the new prototype link and paste it in Dscout. Learn more about how to set a starting point here: Figma - Flow starting points.

Missing page ID

Prototype URL is missing page ID. This may be because the URL has been grabbed incorrectly.

To grab the correct prototype URL:

  1. In your Figma file, make sure nothing is selected. Click the play icon at the top right to enter presentation view.

  2. Click the Share prototype button.

  3. Click "Copy link." Paste in Dscout.

File too large

Figma file is too large to process. This may be because the file has extra pages and frames or is not a dedicated testing file.

To resolve this error, optimize your prototype for testing by removing any pages and frames within the file that are not required for test and then re-sync the prototype in Dscout. You can also copy the prototype flow to a new file (with only content essential for testing in it) and then use this new dedicated testing file in Dscout. Learn more about how to optimize your prototype for testing in Prepare a Figma file for a Dscout study.

No access

The person adding the prototype to Dscout does not have access to the file/prototype in Figma.

To resolve this error, check the share settings in Figma. You’ll need access to both the Figma prototype and Figma file. If the file is part of a project, you will need access to the project as well. Learn more in Figma’s help doc about sharing files and prototypes.

The person who uploaded this prototype hit their rate limit.

Some Figma plans limit API requests from external platforms, including Dscout. This error means the Figma account used to add the prototype has exceeded its request limit.

This can occur when other Dscout studies use prototypes from the same Figma account. Try adding the prototype from another Figma account that can access it. Otherwise, wait and try again later.

Re-sync an updated prototype

Imagine you’re a designer or researcher working on a Figma prototype for a user research mission. You’ve spent a lot of time perfecting the flow and you just launched your mission. After launching, you realize there’s been a new update or adjustment to the prototype—maybe a change in screen size, some optimization, or a wiring fix. But what if you forget? Or what if you need to make changes after launching the mission?

Re-sync anytime, even after launch

You can re-sync your prototype even after the mission has been launched, as long as participants have not completed the task connected to the prototype. This means if any updates are made during the mission, you don’t have to worry about manually tracking changes or contacting your Dscout point of contact to assist with an update.

When should you re-sync a prototype?

Re-syncing is intended for emergency scenarios only, and is not intended for casual use when building a mission. Always exercise caution and confirm that Scouts have not responded to that associated prototype task before proceeding, to avoid introducing inconsistencies to your dataset.

Before launching your mission, you may re-sync if:

  • You decide to make prototype changes during the Create phase

After launching your mission, re-syncing should only be done if:

  • Heat maps or clicks reflect an outdated version of the prototype

  • The prototype has been updated in Figma before participants have interacted with it during the mission

Will re-syncing change what my participants see?

Re-syncing your prototype does not impact the participant’s experience during the mission. Scouts will be linked directly to the most up-to-date version of your prototype as long as the URL is the same.

This Figma prototype's data can't be processed. Please disconnect and reconnect your Figma integration, then try adding the prototype again.

In some cases, Dscout isn't able to parse the data from a Figma prototype. This could be due to a change in the Figma share link or a change in the Figma file itself.

Try to re-sync the prototype. If that doesn't work, disconnect and reconnect your Figma integration, then try the prototype again. For more information, see Disconnect Dscout from Figma.

What happens to analysis tools like the summary and heat maps?

Behavioral data for heat maps and click labeling are derived from the last synced version of the prototype.

  • Analysis tools that rely on prototype data, such as heat maps, will temporarily be disabled during the re-sync process but will be restored as soon as the sync is complete.

  • If you re-sync your prototype after a participant has already completed a task using the old version, the heat maps and click labels will update to reflect the new version. This may cause inconsistencies in the data.

Still need help?

If you have any questions or concerns, please let our Support team know — we'll be happy to help!