---
title: "Verify search ignores stale out-of-order responses"
description: "Use externally delayed sandbox search responses to confirm that a late result for an older query cannot replace the current query results."
canonical_url: "https://vostride.com/agent-library/network-recovery/stale-search-response-order.md"
md_url: "https://vostride.com/agent-library/network-recovery/stale-search-response-order.md"
content_kind: "recipe"
topic: "network-recovery"
---

# Verify search ignores stale out-of-order responses

Use externally delayed sandbox search responses to confirm that a late result for an older query cannot replace the current query results.

## Risk

A search UI can display the newest input alongside results from an earlier request. Intentionally different result sets and controlled response ordering make that mismatch observable without relying on arbitrary delays.

## Fixtures

- An owned sandbox search page with a disposable account and nonoverlapping records for the queries amber and cobalt.
- An external response fixture that holds the amber response until the cobalt response has completed, recording both request and release identities.
- An independent search fixture manifest listing exact expected record identifiers for each query and excluding any overlapping titles.

## Steps

1. Enter amber and verify the input displays amber while the external fixture reports its response is held.
2. Replace the input with cobalt and verify cobalt remains visible; wait for the fixture-confirmed cobalt response and verify only cobalt identifiers appear.
3. Release the held amber response through the external fixture and verify the input and visible result identifiers still correspond to cobalt.
4. Open the first cobalt result and verify its detail identifier and body match the cobalt manifest.
5. Return to search and verify the query remains cobalt with its own results, then inspect the request trace and verify the older response arrived after the newer one.

## Expected results

- The controlled trace proves out-of-order completion, not merely two sequential queries.
- The final result set and opened detail belong to the current cobalt query.
- The late amber response changes neither the visible query nor its current result identities.

## False-pass traps

- Queries sharing records can make a stale response appear correct.
- Typing slowly enough for the first request to finish removes the race being tested.

## Cleanup

- Disable the response-order fixture and clear the disposable account search history if retained.

## 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 first test](/docs/agent-qa/guides/first-test.md)
- [agent-qa hooks](/docs/agent-qa/guides/hooks.md)
- [agent-qa test](/docs/agent-qa/configuration/test.md)

- [Network recovery QA recipes](/agent-library/network-recovery.md)
- [Software factory QA library](/agent-library.md)