---
title: "Verify disabling a feature preserves existing records safely"
description: "Test a sandbox release feature flag with previously created feature data, checking documented access, fallback navigation, and unchanged stored content."
canonical_url: "https://vostride.com/agent-library/release-regression/feature-flag-off-with-existing-data.md"
md_url: "https://vostride.com/agent-library/release-regression/feature-flag-off-with-existing-data.md"
content_kind: "recipe"
topic: "release-regression"
---

# Verify disabling a feature preserves existing records safely

Test a sandbox release feature flag with previously created feature data, checking documented access, fallback navigation, and unchanged stored content.

## Risk

A flag often hides entry points without handling existing records or direct routes. Prepare the data while enabled and evaluate the disabled-state contract explicitly so a missing menu is not mistaken for complete feature gating.

## Fixtures

- An owned sandbox candidate release with a feature flag controlled by an external configuration fixture.
- A disposable record created while the feature was enabled, its saved direct route, and a requirement defining disabled-state read or fallback behavior.
- A read-only record and flag oracle plus a test account authorized for the fixture data.

## Steps

1. Verify the external fixture reports the flag disabled while the previously created record still exists in independent data.
2. Open the relevant navigation area and verify its controls follow the documented disabled-state presentation.
3. Open the saved record route and verify the supported read-only view, fallback, or explicit unavailable message without a broken page or unintended creation action.
4. Return to the main workflow and verify a supported ordinary action still works; inspect the record oracle and verify disabling the flag did not delete or mutate the existing feature data.

## Expected results

- Navigation and direct-route handling follow the same documented disabled-state contract.
- The surrounding core workflow remains usable.
- Existing feature data remains intact unless an explicit approved migration policy says otherwise.

## False-pass traps

- A hidden menu does not prove the old direct route is handled correctly.
- Creating fixtures after disabling the flag may never exercise previously existing feature data.

## Cleanup

- Restore the flag baseline externally and remove the disposable feature record.

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