🐛 Source Gong: extensiveCalls, answeredScorecards, and callTranscripts incremental sync fetches all records on every sync

[humungasaurus]

Summary

Three POST-based streams in source-gong claim to support incremental sync but fetch all records on every sync due to bugs in how fromDateTime is injected into requests.

Affected streams

1. extensiveCalls

Two bugs cause the cursor to never advance:

1. start_time_option injects into request_parameter — but the endpoint (/calls/extensive) is a POST request. Gong ignores query parameters on POST endpoints, so the cursor value computed by DatetimeBasedCursor is silently discarded.
2. request_body_json.filter.fromDateTime is hardcoded to config['start_date'] — this means every sync always filters from the user-configured start date, never from the cursor state.

2. answeredScorecards

The requester still has a stale request_parameters.fromDateTime: "{{ config['start_date'] }}". Since this is a POST endpoint (/stats/activity/scorecards), Gong ignores query params. The incremental cursor already correctly injects into body_json via start_time_option, so this static query param is dead code and a potential conflict.

3. callTranscripts

The stream has request_body_json.filter.fromDateTime hardcoded to config['start_date'] but no incremental_sync block at all. Every sync fetches all transcripts from the original start date.

Expected behavior

• extensiveCalls: start_time_option should inject into body_json with field_path: [filter, fromDateTime], and the hardcoded filter should be removed so the cursor value advances between syncs.
• answeredScorecards: The stale request_parameters.fromDateTime should be removed.
• callTranscripts: The hardcoded filter should be removed and an incremental_sync block with DatetimeBasedCursor should be added, using inject_into: body_json with field_path: [filter, fromDateTime].

Reference

PR #71344 fixed the same class of bug for answeredScorecards (switching inject_into from request_parameter to body_json), but the fixes for extensiveCalls and callTranscripts were missed, and a stale request_parameters entry was left behind on answeredScorecards.

Connector

• Connector: source-gong
• Version: 0.5.5

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11470

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/73f09e4ae843437688f1f166716dfac9

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Daniel Hostetler (@humungasaurus), thank you for reporting this issue — and for the thorough analysis!

I have verified all three bugs by reviewing the connector manifest (source-gong/manifest.yaml):

1. extensiveCalls — Confirmed. start_time_option injects into request_parameter (line ~203), but POST /calls/extensive ignores query params. Additionally, request_body_json.filter.fromDateTime is hardcoded to config['start_date'] (line ~137), so the cursor never advances.

2. answeredScorecards — Confirmed. The stale request_parameters.fromDateTime (line ~278-279) is dead code on the POST endpoint. The incremental_sync block correctly uses body_json (line ~325), so it is not functionally broken but is misleading and should be cleaned up.

3. callTranscripts — Confirmed. Hardcoded request_body_json.filter.fromDateTime (line ~353-355) with no incremental_sync block at all. Every sync re-fetches everything from the start date.

This has been escalated to the internal team for a fix: https://github.com/airbytehq/oncall/issues/11470

---

Need more help? Join Airbyte Community Slack for peer support, or if you are a Cloud customer, open a support ticket referencing this URL.

This message is generated from Devin.ai (internal session link).