When you launch a maze live, we run one last validation check to make sure the test doesn't have any issues that might impact your tester experience.
If there is an issue, we will prevent the maze from going live. One of the errors you might encounter is:
Confirm that you don't have identical paths
A path consists of a sequence of screens. This means that the hotspots used from one screen to the other are not taken into consideration.
This means that, when setting paths, navigating through the same set of screens through different hotspots will show you an error:
You have two identical paths. Please change or remove a path
Confirm that you're not reusing screens in the path
The last screen of a path shouldn't be reused in the same path. Why can't I reuse the last screen in a path?
When the last screen of a path is reused in a path, you'll get a message to remove the screen from the path or change your last screen:
This path cannot contain the end screen from another path
Review your interactive components
If interactive components are enabled on a prototype block, please be aware of a known issue where frames that can be reached only via interactive components are not correctly synced into Maze, but they're still accessible in the prototype preview and can be added to a path.
As a result, when you launch your test live, the unsynced frames are detected, which triggers the "Invalid path" error.
If you believe you're affected by this issue, please let our Support team know.
In the meantime, you can get around this error by detaching the component instances, or by using traditional interactions to link your screens.
Refresh your prototype
Your first step should be refreshing your prototype — sometimes this error happens when there's a one-time sync issue from the prototype you imported.
We recommend reviewing your Mission blocks to ensure that your expected paths are still as intended. Any paths using the affected screens could potentially need to be rebuilt.
Once you've verified everything looks good, you should be able to send the maze live.
Duplicate the affected maze
If fixing any broken paths or refreshing the prototype doesn't address the issue, then the issue may be the result of unexpectedly invalid screen data. In that case, duplicating the affected maze will generally fix any data inconsistencies. Once you've duplicated the affected maze, you should be able to launch the duplicate maze live and delete the original broken one.
We're still working to identify why this issue occurs so we can introduce a more permanent solution that doesn't require duplication. Until then, this solution should enable you to proceed with launching your test live.
Still need help?
If you have any questions or concerns, please let our Support team know — we'll be happy to help!