Delays in Exporting Activities to CRM
minor- Started
- Jun 29, 9:31 AM EDT
- Resolved
- Jul 2, 4:21 PM EDT
- Duration
- 78h 50m
Gong's updates (6)
- investigating · Jun 29, 9:31 AM EDT
We are currently investigating an issue causing delayed event synchronization to the CRM. This is a limited-scope incident, and our engineering team is actively working to identify the root cause. We will provide another update as soon as more information becomes available.
- investigating · Jun 29, 1:27 PM EDT
We are continuing to investigate an issue causing delayed event synchronization to the CRM. A subset of users in the US-hosted environment may experience delays with CRM synchronization. Our engineering team is actively working to identify the root cause, and we will provide another update as soon as more information becomes available.
- identified · Jun 29, 3:55 PM EDT
We have identified the issue causing the CRM synchronization delays. A subset of users in the US-hosted environment may continue to experience delays with CRM event synchronization. We are currently actively working to resolve the issue. Next update as soon as more information becomes available.
- monitoring · Jul 1, 11:49 AM EDT
We identified and resolved the issue that caused delays in exporting activities from Gong to CRM systems. Some customers may still experience delays while the backlog is being processed. Delayed activities will be automatically exported to your CRM, and no action is required on your part. Data syncing from your CRM into Gong is not affected. We’ll share another update as more information becomes available.
- monitoring · Jul 1, 12:06 PM EDT
We identified and resolved the issue that caused delays in exporting activities from Gong to CRM systems. Some customers may still experience delays while the backlog is being processed. Delayed activities will be automatically exported to your CRM, and no action is required on your part. Data syncing from your CRM into Gong is not affected. We’ll share another update as more information becomes available.
- resolved · Jul 2, 4:21 PM EDT
The issue has been resolved.
What our checks recorded
We checked Gong 575 times from Gong's start time to its resolution, once every five minutes. Every one of them reached Gong's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 655 ms, against 620 ms over the 24 hours before. Gong posted the incident at Jun 29, 9:31 AM EDT.
Updates are Gong's own words from its status page (status: resolved); we never add an inferred cause.