> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/integrations/figma-integration/troubleshooting-a-figma-prototype.md).
# Troubleshooting a Figma prototype
If you encounter an error while adding a Figma prototype to your mission, follow the advice below to troubleshoot.
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](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md).
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](https://help.figma.com/hc/en-us/articles/360039823894-Create-and-manage-prototype-flows#h_01HNZT1ATPZP0EAWCQH90CXE42).
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](/study-basics/testing-prototypes/prepare-a-figma-file-for-a-dscout-study.md).
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](https://www.figma.com/exit?url=https%3A%2F%2Fhelp.figma.com%2Fhc%2Fen-us%2Farticles%2F360040531773-Share-files-and-prototypes).
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?
{% hint style="warning" %}
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.
{% endhint %}
**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.
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!
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.dscout.com/integrations/figma-integration/troubleshooting-a-figma-prototype.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.