---
title: "Verify failed export retries retain report scope"
description: "Test a sandbox export job failed by a prepared worker fixture, checking retry identity, retained parameters, and a complete final artifact."
canonical_url: "https://vostride.com/agent-library/reporting-exports/failed-export-retry-same-scope.md"
md_url: "https://vostride.com/agent-library/reporting-exports/failed-export-retry-same-scope.md"
content_kind: "recipe"
topic: "reporting-exports"
---

# Verify failed export retries retain report scope

Test a sandbox export job failed by a prepared worker fixture, checking retry identity, retained parameters, and a complete final artifact.

## Risk

A retry action can accidentally launch the report using current page filters instead of the failed job parameters. Change the visible filter after failure so the original job scope and new UI state are intentionally different.

## Fixtures

- An owned sandbox report with two disjoint saved filters A and B and an independent identifier manifest for each.
- An external worker fixture that fails export A after job creation, then allows its retry to finish.
- A disposable viewer, a job-history oracle, and an artifact parser capable of checking the complete exported identifier set.

## Steps

1. Request export for filter A and verify the externally induced failure appears against the expected job and A parameters.
2. Change the report page to filter B and verify the table now contains B control records.
3. Open the failed A job, choose its supported retry action, and verify the retry review or job metadata retains A scope.
4. Retrieve the completed retry artifact and verify its records match A exactly; inspect job history and verify the relationship to the failed attempt without any B records.

## Expected results

- The retry uses the failed job original parameters despite changed page state.
- The completed artifact contains the complete A dataset and no B controls.
- History records a clear failed-attempt and successful-retry relationship.

## False-pass traps

- Retrying before changing page filters may hide a current-state parameter bug.
- A completed job label cannot establish that the correct dataset was generated.

## Cleanup

- Delete the failed and completed sandbox artifacts and disable the worker failure rule.

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

- [Reporting and export QA recipes](/agent-library/reporting-exports.md)
- [Software factory QA library](/agent-library.md)