---
title: "Reload a nested record route directly"
description: "Verify that a nested record URL loads the intended detail after a full reload rather than depending on prior client-side navigation state."
canonical_url: "https://vostride.com/agent-library/navigation-routing/deep-link-reload.md"
md_url: "https://vostride.com/agent-library/navigation-routing/deep-link-reload.md"
content_kind: "recipe"
topic: "navigation-routing"
---

# Reload a nested record route directly

Verify that a nested record URL loads the intended detail after a full reload rather than depending on prior client-side navigation state.

## Risk

Client navigation can succeed while direct requests to the same route fail at the server or omit required context. A prepared nested record gives the route a stable identity oracle.

## Fixtures

- A test workspace contains project QA Routing and issue ROUTE-31 with a distinctive body sentence.
- The seed manifest provides the expected nested application path and immutable issue identifier.
- The QA account has a valid named auth state for the configured target and permission to the test workspace.

## Steps

1. Open the workspace through normal navigation and verify the QA account and project context.
2. Open ROUTE-31 and verify its key, title, and distinctive body sentence.
3. Reload the browser while on the nested issue route and verify the same detail returns without a generic not-found page.
4. Navigate away to the project list, then open the prepared nested path directly through the configured application origin.
5. Verify the issue key, project breadcrumb, and body agree with the seed manifest after direct loading.

## Expected results

- The direct route and client-navigation route resolve to the same immutable issue.
- A full reload preserves enough routing and authentication context to render the intended detail.
- The expected project breadcrumb and body distinguish the record from a generic application shell.

## False-pass traps

- A visible sidebar with an empty main region does not establish a successful nested-route load.
- Manually navigating through the list after a reload error would conceal the direct-request defect.

## Cleanup

- Delete the routing fixture issue and project if disposable.

## 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)