---
title: "Verify candidate workers process previously queued jobs"
description: "Test an externally preserved sandbox job created by the previous release, checking candidate worker compatibility and the resulting user-visible record."
canonical_url: "https://vostride.com/agent-library/release-regression/queued-job-old-payload.md"
md_url: "https://vostride.com/agent-library/release-regression/queued-job-old-payload.md"
content_kind: "recipe"
topic: "release-regression"
---

# Verify candidate workers process previously queued jobs

Test an externally preserved sandbox job created by the previous release, checking candidate worker compatibility and the resulting user-visible record.

## Risk

Queued jobs outlive deployments and can carry older payload schemas. Creating the job with the candidate code misses that boundary, so the external fixture must preserve a genuine previous-version payload and original job identity.

## Fixtures

- An owned sandbox queue containing a held job created by the previous release to generate a harmless summary record.
- An external deployment fixture that has installed the candidate worker and can release the original queued job, reporting both producer and worker versions.
- A read-only job and summary oracle with expected source identifiers, content fields, and one logical completion result.

## Steps

1. Open the job status page and verify the prepared previous-release job identifier and pending state before release.
2. Release the external queue hold and verify the candidate worker reaches a terminal completed state for that original job.
3. Open the resulting summary through the product UI and verify its source references and expected content fields are complete.
4. Inspect the independent job and result oracle and verify one logical completion and one summary, with no schema-related dead-letter entry or duplicate result from retries.

## Expected results

- The candidate worker accepts the actual previous-producer payload contract.
- The result retains all required source references and content.
- The original job has one effective completion without an unresolved failure copy.

## False-pass traps

- Recreating the job with candidate code replaces the old payload under test.
- A completed queue status can hide an empty or incorrectly linked result record.

## Cleanup

- Delete the generated summary and clear the isolated old-payload job 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)