Skip to main content
matthew_lind
VIP ⭐️⭐️⭐️⭐️⭐️
August 4, 2022
New Idea

Gong Integration: Adjust Execution Log status to something other than "Failed" if no Gong records meet filter criteria

Related products:CS Timeline & Activity Tracking
  • August 4, 2022
  • 2 replies
  • 79 views

Proposal to amend the Execution Log within the Gong-Timeline integration to more clearly denote “Failed” versus 0 Gong records in scope.

Currently, if no Gong records are meet the filter criteria, the Execution Log reports a Status of “Failed”. However, this is misleading, because the integration is working exactly as designed, and simply had 0 records meeting the filter criteria.

I contrast this with Connectors 2.0 Execution Activities. logs, where if 0 records meet the criteria, the job status is “Success” with a “Success Count” of 0 records.

I propose this for two reasons:

  1. Consistency of presentation across Gainsight features. Consistency in how integration logs are presented leads to speed, accuracy, data quality and ease of use.
  2. A “Failed” Status in the Gong integration logs can be a “false positive”, because often there is no actual problem or failure to address.

 

2 replies

Contributor ⭐️⭐️
November 19, 2024

We are having the same issue with the filter criteria being ignored for the Gong integration. At times we have over 600 “failures” in the Execution Log that are not actually failures to sync. It includes calls that don’t meet the criteria for the sync and don’t have a Company in Gong.

A fix for this would be greatly appreciated.

romihache
VIP ⭐️⭐️⭐️⭐️⭐️
November 6, 2025

We're about to trial Gong and are finding all of these caveats as we go.
Adding my vote to this idea, please make the logs consistent with the experience we get in the rest of the platform. It's very confusing and misleading for a successful-but-empty run to be flagged as "Failed."

Continuous improvement is better than delayed perfection