---
title: "Verify sync ignores obsolete status events"
description: "Check an owned sandbox integration with externally reordered status events, ensuring an older update cannot overwrite the current source revision."
canonical_url: "https://vostride.com/agent-library/integrations-sync/out-of-order-status-events.md"
md_url: "https://vostride.com/agent-library/integrations-sync/out-of-order-status-events.md"
content_kind: "recipe"
topic: "integrations-sync"
---

# Verify sync ignores obsolete status events

Check an owned sandbox integration with externally reordered status events, ensuring an older update cannot overwrite the current source revision.

## Risk

Arrival order and source order are different. An integration that applies the last received payload blindly can regress a completed task to an earlier state even while every delivery reports success.

## Fixtures

- An owned sandbox source and destination connected through the integration under test, with one disposable task.
- An external delivery fixture containing revision 10 In progress and revision 11 Done, prepared to deliver 11 before 10.
- A read-only source revision manifest and destination audit oracle with immutable task and event identifiers.

## Steps

1. Verify the destination task starts at the recorded baseline and the integration activity belongs to the intended sandbox connection.
2. Deliver revision 11 externally and verify the destination shows Done with the expected source reference.
3. Deliver the older revision 10 and verify the destination remains Done after the integration reports terminal processing.
4. Inspect the independent audit oracle and verify revision 10 was ignored, recorded as obsolete, or reconciled under the documented ordering policy without regressing the final state.

## Expected results

- The final destination state corresponds to the latest source revision.
- The task identity and source reference remain stable across both deliveries.
- The audit trail explains handling of the older event without an effective backward transition.

## False-pass traps

- Delivering in normal revision order does not exercise stale-event protection.
- A final Done badge checked before older-event processing completes can hide a delayed regression.

## Cleanup

- Remove the disposable task and clear the external reordered-delivery 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)

- [Integration and synchronization QA recipes](/agent-library/integrations-sync.md)
- [Software factory QA library](/agent-library.md)