Test Adapter Disconnects Before They Happen in Production

Adapters disconnect eventually, and the difference between a routine blip and a state integrity incident is whether anyone tested the disconnect path first.

The disconnect is guaranteed; only the timing is unknown. Testing it converts a future incident into a known behavior with a runbook.

Disconnect scenarios to rehearse

• Mid-write disconnect: does the write land, roll back, or dangle?
• Reconnect after minutes: does the adapter replay, resync, or duplicate?
• Permanent loss: does queued work route to a fallback or a dead letter?

Use the adapter system, threat model, and examples to know what a disconnect does before production shows you.