---
title: "Verify incompatible sync records are isolated and recoverable"
description: "Test an owned sandbox connector with one schema-incompatible source record, checking clear isolation, continued valid imports, and repair of the failed item."
canonical_url: "https://vostride.com/agent-library/integrations-sync/schema-change-quarantines-record.md"
md_url: "https://vostride.com/agent-library/integrations-sync/schema-change-quarantines-record.md"
content_kind: "recipe"
topic: "integrations-sync"
---

# Verify incompatible sync records are isolated and recoverable

Test an owned sandbox connector with one schema-incompatible source record, checking clear isolation, continued valid imports, and repair of the failed item.

## Risk

One malformed record should follow the product batch-failure policy rather than silently disappear or block unrelated data indefinitely. Separate the failed record identity from successful batch counts and verify a repair using the same source identity.

## Fixtures

- An owned sandbox source batch containing two valid records and one record with a field incompatible with the destination schema.
- A product specification for quarantine or batch failure and an external source fixture able to correct the incompatible value.
- A read-only import ledger and destination oracle with exact expected valid and failed identifiers.

## Steps

1. Run the prepared sync batch and verify the UI reports the incompatible record with a specific field-related error under the documented batch policy.
2. Inspect valid destination records and verify their presence or intentional noncommit state matches that same policy rather than an assumed partial success.
3. Correct the incompatible source value through the external fixture and use the supported retry or next-sync path.
4. Verify the repaired record imports with its original source identity; inspect the independent ledger and confirm complete final coverage without duplicate valid records or a silently unresolved quarantine.

## Expected results

- The incompatible record remains explicitly traceable to its source identity and field error.
- Other records follow the documented atomic or partial batch policy.
- Repair produces one correct destination mapping and resolves the earlier failure.

## False-pass traps

- A generic completed status can hide a silently dropped incompatible record.
- Creating a new source record instead of repairing the original bypasses quarantine recovery.

## Cleanup

- Remove the synthetic batch records and clear their resolved import-error fixtures.

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