Some Gong Calls Are Not Syncing to the Destination

Issue

Some Gong calls available through the Gong API are missing from the destination.

Environment

Connector: Gong

Resolution

To resolve this issue, wait for the next weekly re-import sync, which re-imports the last six months of Gong data, and check whether the missing calls appear. For more information, see our Gong sync overview.

If the calls are still missing after the next re-import sync, contact our support team.

To check whether the Gong API returns records with a delay:

1. Run a Gong API query for a recent four-hour window.
2. Run the same query again 24 hours later.
3. Compare the results.
4. If additional records appear in the later query, report the discrepancy to Gong.

Cause

Fivetran incrementally syncs call records based on the data available from the Gong API during each sync. This issue occurs when the Gong API makes a call record available after its original sync window has passed. When this happens, we may not pick it up during an incremental sync because the record retains its original timestamp.

Our weekly re-import of the last six months of Gong data captures these late-arriving records.