---
title: "Recover from an unknown application route"
description: "Verify a nonexistent route shows the product not-found state and its visible recovery action returns to a working application page."
canonical_url: "https://vostride.com/agent-library/navigation-routing/unknown-route-recovery.md"
md_url: "https://vostride.com/agent-library/navigation-routing/unknown-route-recovery.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Recover from an unknown application route

Verify a nonexistent route shows the product not-found state and its visible recovery action returns to a working application page.

## Risk

A custom not-found view should be distinguishable from a server error or empty shell. This UI scenario validates rendering and recovery; HTTP status claims require a separate approved request check.

## Fixtures

- A prepared nonexistent path contains a run-specific suffix and is absent from the application route and record fixtures.
- The product not-found design provides a Home or Dashboard recovery action.
- The QA target is a test environment with a known working dashboard and a distinct account marker.

## Steps

1. Open the prepared nonexistent path within the configured application origin.
2. Verify the visible page explains that the requested destination was not found and offers the expected recovery action.
3. Verify no unrelated record detail is presented under the unknown path.
4. Activate the recovery action and verify the known dashboard and account marker appear.
5. If HTTP status is an explicit requirement, run the prepared request verifier for the same nonexistent path and compare its status to the product contract.

## Expected results

- The unknown path produces an informative not-found UI rather than endless loading or an unhandled error.
- The recovery action reaches the known working application destination.
- Any asserted HTTP status comes from the independent request verifier, since screenshots do not expose response semantics.

## False-pass traps

- A visually branded page can still return an incorrect HTTP status; separate that requirement from UI rendering.
- A path that accidentally names a real fixture would invalidate the missing-route premise.

## Cleanup

- Remove any temporary navigation preferences or route fixture overrides created for the run.

## Use with agent-qa

Adapt this test design to your application's acceptance criteria and configured target using the [recipe execution guide](/agent-library/software-factory/turn-a-recipe-into-an-agent-qa-test.md). External fixture setup and non-UI checks require your own supported hooks or test tooling. Validate the authored test, execute it, and inspect the completed evidence; this recipe is not a recorded test result.

## References

- [agent-qa test](/docs/agent-qa/configuration/test.md)
- [agent-qa first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa web testing](/docs/agent-qa/guides/web-testing.md)

- [Navigation and routing QA recipes](/agent-library/navigation-routing.md)
- [Software factory QA library](/agent-library.md)