---
title: "Verify disconnecting an integration stops inbound changes"
description: "Test an owned sandbox connector after disconnection, checking that later prepared source events cannot update destination records or silently reconnect."
canonical_url: "https://vostride.com/agent-library/integrations-sync/disconnect-stops-inbound-writes.md"
md_url: "https://vostride.com/agent-library/integrations-sync/disconnect-stops-inbound-writes.md"
content_kind: "recipe"
topic: "integrations-sync"
---

# Verify disconnecting an integration stops inbound changes

Test an owned sandbox connector after disconnection, checking that later prepared source events cannot update destination records or silently reconnect.

## Risk

Disconnection can remove the UI card while leaving an active webhook or queued processor. Cross a post-disconnect processing checkpoint and inspect actual destination revisions, not only the missing connector badge.

## Fixtures

- An owned sandbox connection with one synchronized disposable record and its baseline destination revision.
- An external event fixture prepared to send one later source update after the product disconnect operation completes.
- A read-only connection, queue, and destination oracle documenting whether existing imported records are retained when disconnecting.

## Steps

1. Open connection settings and verify the intended source account and destination workspace before choosing Disconnect.
2. Confirm disconnection through the product flow and verify its visible disconnected state and documented treatment of existing imported data.
3. Deliver the prepared later source event externally and complete the sandbox processor checkpoint, verifying the fixture reports terminal handling.
4. Inspect the destination and connection oracles and verify no effective update from the later event or recreated connection. If the policy retains imported data, reopen the record and verify its content remains at the pre-disconnect revision. If the policy deletes imported data, verify the record remains absent and the later event has not recreated it.

## Expected results

- The connection remains disconnected after a later inbound event is processed.
- The post-disconnect source update neither changes retained destination content nor recreates deleted destination data.
- Existing imported data follows the documented retention policy.

## False-pass traps

- A removed settings card cannot prove an inbound webhook consumer was disabled.
- Checking before queued processing completes can miss a delayed unauthorized update.

## Cleanup

- Remove the sandbox connection remnants and disposable synchronized record according to fixture policy.

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