Clari Outage History

On 2026-05-11 at approximately 18:55 UTC, a number of Clari customers encountered errors connecting to the Salesforce integration within the Clari application. Engineers identified a configuration change that enabled a 30-day idle timeout for Salesforce refresh tokens, which caused integration user sessions to be invalidated and disconnected across multiple organizations. The setting was disabled at approximately 19:15 UTC, after which availability began recovering. Full service availability was confirmed for all affected organizations by approximately 20:52 UTC. Other areas of the Clari application were unaffected during this time.

On 2025-05-08 at approximately 02:52 UTC, customers experienced delays of several hours with RevDB CRM sync jobs due to an internal service connectivity issue impacting the workflow system responsible for processing syncs. The affected services were restored and the backlog was fully cleared. No data was lost or compromised during the incident. Additional monitoring and recovery safeguards have since been implemented to reduce the risk of recurrence.

On 2026-04-09 at approximately 14:48 UTC, users were unable to load Analytics modules in the Clari application. Clari engineers quickly identified the cause and took action to restore the affected functionality. During this time, a small number of other areas of the application were also impacted as a result of the same underlying issue. Engineers performed rolling restarts of the affected Analytics services, restoring full Analytics module availability by approximately 16:21 UTC. Isolated issues in a small number of other dependent services were subsequently identified and resolved through additional targeted restarts, with all issues fully cleared by 17:52 UTC.

On 2026-04-08 at approximately 18:53 UTC, all Clari customers lost access to the Forecast tab in the Clari application. Other areas of the application were unaffected and continued to operate normally. Clari engineers quickly identified the cause as the unintended deletion of configuration data required to display the Forecast tab, and restored the affected data. During the restoration process, there was a brief period of increased latency as service capacity scaled back up to handle returning traffic. Full access to the Forecast tab was confirmed for all affected users by 23:20 UTC.

At 14:30 UTC on March 25, 2025, Clari Copilot experienced an interruption in email notifications due to an exhausted email delivery quota. As a result, email notifications scheduled during this period were not delivered. Clari was able to increase the delivery limit and service was fully restored as of 14:55 UTC on March 27, 2025. All systems are now performing as expected and emails are being delivered. Please note that missed notifications from the outage window cannot be retroactively delivered. At no time during this incident was user data at risk.

At approximately 2026-03-04 15:00 UTC, a subset of Clari Copilot customers experienced an issue where the recording bot was unable to join Zoom meetings. This was caused by an account authentication error within the Zoom platform that prevented the bot from successfully joining calls. This was a reoccurrence of the issue that prevented Copilot from joining Zoom calls on 2026-02-11 and was caused by Zoom not fully updating the Copilot authentication across their entire platform. The Clari engineering team worked with Zoom’s Support and Development team to correctly update the authentication process platform wide and resolve the issue. An RCA from Zoom on this issue is pending. Recording functionality was fully restored and confirmed operational at 2026-03-05 11:28 UTC.

Around 2026-02-11 09:51 UTC an issue affecting links in some email content resulted in bounced or spam-foldered emails by a third party vendor \(Google\). The team has worked closely with the vendor \(Google\) and successfully remediated the situation by 2026-02-12 06:00 UTC.

At 11:11 UTC on February 4, 2026, a subset of Clari Copilot customers experienced an issue where the recording bot was unable to join Zoom meetings. This was caused by an account authentication error with the Zoom platform that prevented the bot from successfully joining calls.The Clari engineering team worked with Zoom’s development team to update the authentication process and resolve the issue. Recording functionality was fully restored and confirmed operational at 12:05 UTC on February 9, 2026. We regret that scheduled calls for impacted customers during this window were not recorded.

On 2026-01-14 at approximately 08:00 UTC, Clari made a system update that caused the user-defined column order in Opportunity Grid saved views to be re-ordered or reverted to the default column ordering. The issue caused workflow disruption and inconvenience for users but did not block core business operations or impact data integrity. At 2026-01-14 15:52 UTC the Clari Engineering team successfully reverted the change and all user-defined saved views were restored.

Starting around 2026-01-11 at 02:45 UTC, a few Clari customers may have seen page load errors when attempting to access areas of the app including Forecasting and Analytics. This was caused by an error introduced while preparing these customers for migration to RevDB. Clari Engineering corrected the database entries and the impacted customers were fully restored by 2026-01-12 18:15 UTC. No customer data was impacted and there is no impact to any RevDB migrations.

On 2026-01-05 at approximately 13:50 UTC, Clari experienced an interruption in the processing of CRM and Activity data into RevDB. Due to database locking issues across multiple clusters, live CRM and Activity updates stalled for some customers, resulting in data freshness delays of roughly 2 to 5 hours. The impact was limited to delayed data updates; the application experience was unaffected, and no customer data was lost. Clari engineers identified a buildup of long-running, idle-in-transaction database sessions that were causing lock contention. The problematic sessions were terminated, unblocking the affected clusters and allowing CRM and Activity ingestion to resume. To reduce the likelihood of this issue recurring, Clari has implemented changes to prevent idle sessions from accumulating, and we are strengthening monitoring and alerting for database lock behavior to detect and quickly mitigate similar conditions.

On 2025-12-18 at approximately 12:00 UTC, a change by Google to the Google Meet web UI began to be rolled out that affected Copilot’s ability to record calls for a subset of customers using Google Meets. Between 13:05 UTC and 14:20 UTC some calls with MS Teams and Zoom were also impacted and not recorded. Clari made an update to Copilot to account for the updated UI and recording functionality was fully restored by 2025-12-18 at 16:45 UTC. For the impacted customers, calls scheduled during this period were not recorded.

On 2025-12-11 at approximately 23:00 UTC, a change by Google to the Google Meet web UI began to be rolled out that affected Copilot’s ability to record calls for a subset of customers. Clari made an update to Copilot to account for the updated UI and recording functionality was fully restored by 2025-12-13 at 18:35 UTC. For a small subset of customers, Google Meet calls scheduled during this period were not recorded. All Zoom and Microsoft Teams calls continued to record successfully and were unaffected.

Between 2025-12-09 11:08:00 UTC and 2025-12-09 16:25:26 UTC Clari experienced a delay in synchronization of CRM data to RevDB. Customers saw stale data and degraded performance of Clari Web Application. The issue was caused due to a database contention and was resolved by identifying and fixing the source of blocking queries. After the fix we monitored the database and after observing stable performance for a period of time it was confirmed that the issue was fully resolved. No user data was at risk or damaged by this incident.

Between 15:45 UTC on 29 October and 00:05 UTC on 30 October 2025, Clari customers were not able to use the Groove Outlook Add-in due to a Microsoft Azure outage. See the Microsoft Azure status page for full details, [https://azure.status.microsoft/en-us/status/history](https://azure.status.microsoft/en-us/status/history). The Azure service was restored at 00:05 UTC on 30 October 2025, at which time the Groove Outlook Add-in returned to normal functionality. No customer data was at risk during this incident.

On Friday October 10th, during our Copilot authentication migration, we made network changes that were inadvertently applied in a temporary state. When that state reverted, we lost connectivity to the migrated auth service. This was a one-time activity, and we’ve updated our procedures and system controls to prevent a recurrence

On 2025-08-14 14:09:39 UTC, we identified an issue that temporarily prevented new Google Calendar events from syncing with Groove. The Clari Engineering team traced the issue to a recent change and reverted it at 2025-08-14 15:10:41 UTC, which resolved the technical issue. Following the fix, synchronization resumed and affected events in the queue gradually propagated. By 2025-08-14 21:11:23 UTC, all impacted events had been successfully synchronized and were visible in Groove. Other areas of the Clari Platform were unaffected. No customer data was impacted or lost as a result of this incident.

On 2025-08-13 at 11:13:50 UTC, the Clari team detected an issue that prevented users from being able to log into the Knowledge Center or contact Clari Support through the Support Portal. The Clari Engineering team reverted a recent change which resolved the issue and the ability to contact Support was restored at 2025-08-13 14:06:00 UTC. Other areas of the Clari Platform were unaffected. No customer data was impacted or lost as a result of this incident.

On 2025-07-21 at 23:30 UTC, Clari detected an issue caused by a change in the Google Meet web UI that affected Copilot’s ability to record calls. A partial outage began around 2025-07-21 at 21:00 UTC. The recording functionality was fully restored by 2025-07-22 at 14:32 UTC. Google Meet calls scheduled during this period were not recorded. All Zoom and Microsoft Teams calls continued to record successfully and were unaffected.

On 2025-07-21 at 13:59 UTC, we detected elevated error rates in our authentication service, causing some users to be automatically logged out. The issue was resolved by increasing the rate limit with our auth provider, and service was fully restored by 15:37 UTC. No customer data was impacted or lost as a result of this incident.