---
title: "Verify a prepared rollback can read candidate-created data"
description: "Check an externally rolled-back sandbox release against records created by the candidate, verifying readable detail and supported edits after rollback."
canonical_url: "https://vostride.com/agent-library/release-regression/rollback-reads-newly-created-record.md"
md_url: "https://vostride.com/agent-library/release-regression/rollback-reads-newly-created-record.md"
content_kind: "recipe"
topic: "release-regression"
---

# Verify a prepared rollback can read candidate-created data

Check an externally rolled-back sandbox release against records created by the candidate, verifying readable detail and supported edits after rollback.

## Risk

Application rollback can leave data written in a newer shape. This recipe evaluates the declared compatibility contract in an isolated environment; it does not authorize deployment changes or destructive database reversal.

## Fixtures

- An owned sandbox snapshot containing a record created by the candidate release with both existing and newly introduced fields.
- An external release workflow that has already restored the previous supported app version while retaining the candidate-created data.
- A documented rollback data-compatibility policy and read-only record oracle capturing the original candidate record shape and identifier.

## Steps

1. Verify the external fixture reports the rolled-back app version and retained candidate-created record before opening the product.
2. Find and open that record through the previous app UI, verifying its identity and every field promised by the compatibility policy.
3. Edit one backward-compatible field, save, and verify the reopened detail shows the change without a fatal schema error.
4. Inspect the independent record oracle and verify the identifier remains stable and newer fields are preserved or intentionally transformed exactly as the documented policy requires.

## Expected results

- The previous app can read the candidate-created record under the declared rollback contract.
- A supported edit persists without unintended loss of newer data.
- The retained record identity and compatibility transformations match the independent baseline policy.

## False-pass traps

- Rolling back both application and data skips the compatibility condition this recipe targets.
- A list title alone does not prove the previous version can open or edit the record.

## Cleanup

- Retire the isolated rollback snapshot or restore its test record through the external release fixture.

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

- [Release regression QA recipes](/agent-library/release-regression.md)
- [Software factory QA library](/agent-library.md)