---
title: "Verify live-feed reconnect fills missed events"
description: "Check an externally interrupted sandbox live feed to ensure reconnect restores events created during the gap without duplicates or incorrect ordering."
canonical_url: "https://vostride.com/agent-library/network-recovery/reconnect-live-feed-gap.md"
md_url: "https://vostride.com/agent-library/network-recovery/reconnect-live-feed-gap.md"
content_kind: "recipe"
topic: "network-recovery"
---

# Verify live-feed reconnect fills missed events

Check an externally interrupted sandbox live feed to ensure reconnect restores events created during the gap without duplicates or incorrect ordering.

## Risk

A connected status badge proves transport recovery but says nothing about missed events. Record the event sequence outside the UI and include events produced before, during, and after the disconnection.

## Fixtures

- An owned sandbox activity feed with a disposable account and a known empty starting cursor.
- An external connection fixture that interrupts the live stream while a separate sandbox producer emits numbered events E1 through E5.
- A project-owned event ledger with stable identifiers, ordering keys, and the product contract for reconnect catch-up.

## Steps

1. Publish E1 through the external producer and verify its exact identifier and body appear once in the connected feed.
2. Confirm the external stream interruption, publish E2 and E3, and verify the UI accurately indicates reconnection or stale status.
3. Restore the stream through the fixture and verify E2 and E3 appear alongside E1 once catch-up completes.
4. Publish E4 and E5 after reconnection and verify all five identifiers appear exactly once in the documented ordering.
5. Leave and reopen the feed, verify the same complete event set, and compare the independent event ledger and stream trace with the displayed sequence.

## Expected results

- Events created while disconnected are recovered from the authoritative event history.
- The final feed contains exactly E1 through E5 with no duplicate replay rows.
- The ordering follows the documented event key, including the two gap events.

## False-pass traps

- A restored Connected badge can coexist with a permanently missing event gap.
- Comparing only row counts misses a duplicated event replacing a missing one.

## Cleanup

- Delete the sandbox feed events and disable the external stream interruption.

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

- [Network recovery QA recipes](/agent-library/network-recovery.md)
- [Software factory QA library](/agent-library.md)