|
Learn how to troubleshoot issues with your Figma Task setup or analysis — including common error messages, quality concerns, FAQs, and helpful support links. |
This article applies to: UserTesting
On this page:
Error messages
Here are common error messages you may see when connecting a Figma prototype, plus causes and fixes.
| Error message | Likely cause | Suggested fix |
| That doesn’t look like a Figma link. Please double-check or consider using another task type. | The link entered is not a Figma link. |
Ensure the link is a complete Figma URL. If testing a non-Figma prototype, try using the Navigation task instead. |
| This link isn’t supported or may be incomplete. Please enter a full Figma prototype link. | The URL might be a valid Figma file but not configured as a prototype. | Verify that the link leads to the correct Figma prototype. |
| Looks like this file doesn't exist or you don't have access. Please double-check. | The link may not exist, or you may not have access to it. | Confirm you have the required permissions and that the link is valid. |
| We couldn’t connect your Figma prototype. Please try again. | This could be due to a connection issue. | Check your internet connection, refresh the page, and try again. |
| Looks like this link is incomplete. Please open the prototype in your browser and copy the full link. | The Figma link is missing key parameters (e.g., Node-ID). | Open the prototype in your browser, copy the full URL from the address bar, and try again. |
Known issues
Issues that may not show errors but can affect test results or participant experience.
|
Problem |
Likely Cause |
Suggested Fix |
|
Success path not tracking |
The prototype was edited after launch, breaking the interactions. |
Avoid editing prototypes or success paths after launch. |
|
Missing or slow-loading frames |
Prototypes with many images or complex transitions can lag. |
Optimize the prototype’s file size and test in incognito mode. |
|
Participants not progressing |
The password wasn’t included in the task instructions. |
Either remove the password or clearly include it in the instructions. |
|
Participants can’t find the right clickable areas. |
Thoroughly test the prototype to ensure navigation is clear |
|
|
Participants don't know to click Next after completing a task. |
Ensure task instructions are clear about required actions. |
|
|
Single component clicks generate multiple steps in my results |
The prototype has multiple interactions set up on a single component. |
Limit to one interaction per component to avoid duplicate steps in the results. |
FAQs
Q: Can I edit my prototype after the test starts?
A: Technically yes, but we strongly advise against it — especially if you’ve defined a success path. Edits can break results tracking. If significant updates are needed, duplicate the test and relaunch.
Q: Can I run a Figma test on Mobile?
A: Yes! The Settings module in the Test Builder allows you to set mobile targeting. Be sure to test your prototype on mobile using the preview, and take extra care to remove hover states, as these won’t trigger on mobile devices.
Q: How many Figma tasks can I have on a test?
A: There is no hard limit on the number of Figma tasks on an Interaction Test. That said, we strongly advise keeping the number low and that you take into consideration the length of each Figma task in order to ensure that participants remain engaged and feedback quality is high as a result.
Q: Why isn’t my success path showing up in results?
A: Success paths only show if they were defined before launch. Editing or removing key components or pages from the success path after launch will prevent proper tracking. Additionally, there can be a delay in the time taken for data to process - please allow a reasonable period of time for the data to fully populate.
Q: Can I run a Figma Task without a success path?
A: Absolutely! Success paths are optional. You’ll still get full interaction data — including click paths, screen views, and session recordings.
Q: Why can’t participants move to the next task automatically?
A: Figma Tasks are intentionally set up to give participants time to complete interactions. They must click “Next” manually — be sure to call this out in your task instructions.
Q: How do I know if something broke during the test?
A: Monitor your first few sessions and watch recordings. This will help you spot any issues with the task or your prototype.
Getting more help
💡If you're still stuck, contact customer support for personalized guidance.
Related content
|
|
|
|
Want to learn more? Check out these Knowledge Base articles... |
Interested in growing your skills? Check out our University courses... |
|
|
|
|
Need hands-on training? |
Can't find your answer? |