Guides
Inspect a Guide route map
Trace page order and authored actions, find missing destinations, and review unreachable pages or loops.
The Route map in Warnings shows how page order and authored actions connect a Guide. Use it to find broken destinations and content outside the start path.
Open an editable Guide, then use its whole-Guide Warnings review.
Trace a path
- Check Start for the starting page. If it is missing, correct the Guide's start sequence first.
- Compare Reachable with the total number of pages.
- Review Routes and Path issues, then scroll through Route map.
- Read each route's source, destination, type, and any warning.
- Select Source, Edit route, or Target when available.
- Save changes and test the result in Preview and Play.
Routes include page order, page-entry actions, timer completion, block taps, Field after-submit actions, option selection, and popup destinations. Conditional indicates an action that depends on interaction, such as tapping or submitting an answer. It does not mean that every condition has been exercised.
Edit route opens the source block when a block owns the action. For page-entry and timer actions, use Source and the page's settings.
Resolve findings
| Finding | What to inspect |
|---|---|
| Missing target | An action has no complete page or sequence destination |
| Stale target | The stored destination no longer exists |
| Unavailable outcome | The configured action cannot currently resolve |
| Unreachable page or sequence | No page-order or authored route reaches it from the configured start |
| Path stops before all pages | A reachable endpoint leaves other authored pages outside the path |
| No-exit loop | A reachable cycle has no detected forward or Close/Finish exit |
An unreachable sequence may be intentional reference material, but verify how the intended player reaches it. Choosing a sequence manually is different from a route from the start.
Popup targets are treated as reachable content with a return to their source. A popup alone is not a terminal Finish action.
Read the counts carefully
The route list includes ordinary next-page connections as well as authored actions. The summary's authored-action count can therefore differ from the number of listed routes. Path-issue and toolbar-warning totals also count different findings.
Reachability is a structural analysis. In particular, ordinary page-order connections can appear even where manual controls are hidden or locked. The map does not simulate a player's answers, preferences, media readiness, or timer timing. Required Fields can still block a route marked available.
A Guide with no detected route issues may still need accessibility and playback testing. Conversely, optional reference pages may deliberately sit outside the main path. Use the findings to inspect intent rather than deleting content merely to reduce a count.
For actual movement rules, see navigation locks, page outcomes, and answer actions.