Which connector?: Gong

Allow a shallow daily replay and a deep periodic replay to run concurrently on the same connection. for example a daily replay with a short lookback for freshness, alongside a weekly or monthly deep replay for recovery.

Additional details:

The Gong connector currently supports only one replay sync strategy at a time. This forces a choice between two failure modes, both of which are damaging:

• Weekly 180-day replay (current): deep but infrequent. Our call table runs at roughly 20% completeness Monday through Thursday  23 calls recorded on 27 July against a normal weekday volume of 130–180 and only reconciles when Friday's replay runs. Downstream consumers get badly incomplete data for four days of every five.
• Daily 1-day replay (offered as interim): fresh but shallow. Nothing recovers a skipped record except a replay, so any record the source doesn't serve within 24 hours is lost permanently.

We cannot pick one without accepting a serious cost. What we need is a shallow, frequent replay for freshness plus a deep, periodic replay as a safety net.