Is Clari Down Right Now? Check if there is a current outage ongoing.

We're currently experiencing an issue with our third party provider, (link to google status). Some of Groove services are impacted and won't function properly. Our team is actively investigating.

MS Teams recordings are experiencing higher than expected error rates. Our engineering team is actively investigating.

We are currently experiencing a severe outage affecting Groove and Groove Dialer. The issue began approximately one hour ago and is preventing users from logging in or using the services. Our engineering team is actively investigating and working to restore functionality. The probable cause appears to be an issue with a third-party computing service. We will provide further updates as we learn more. Our engineering team is actively investigating.

On May 22, 2025, between 15:51 and 16:42 UTC, some users experienced a blank Groove Task Pane when accessing the Outlook Add-In via both Desktop and Web. The issue was isolated to users on slower network connections, and not all customers were affected. Our team identified the root cause and implemented a fix, restoring full functionality. We apologize for the disruption and appreciate your patience as we worked to resolve the issue.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

We’re aware that the Outlook Add‑In on both desktop and web may intermittently appear blank. We're currently investigating the issue, and will provide an update soon.

Some customers may be seeing problems with Desktop Outlook Add-In. Our engineering team is actively investigating.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

We’re aware that the Outlook Add‑In on both desktop and web may intermittently appear blank. We're currently investigating the issue, and will provide an update soon.

Some customers may be seeing problems with Desktop Outlook Add-In. Our engineering team is actively investigating.

On 2025-05-20 at 17:01 UTC Clari received reports that the Opportunities module was not loading. It was found that users whose default view was not set to the Opportunities module were unable to access Opportunities. At 17:42 UTC Clari rolled back a change which restored service for all users. Approximately 10% of Clari Core customers were affected. No customer data was impacted or lost as a result of this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Some users are currently unable to access the Opportunities module in the Clari app. Our team is actively investigating the issue.

On 2025-06-06 approximately 17:30 UTC, Clari detected that RevDB data was delayed for 70% of customers, leading to data becoming stale in RevDB-powered features such as Analyze and Account Inspection. RevDB data caught up for all customers by 2025-05-07 1:00 UTC.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

The team has identified the issue, and applied the fix. We are currently monitoring.

We have detected delays in RevDB data pipelines that are affecting many (though not all) customers. This will cause data to become stale in RevDB-powered features, which includes Analyze and Account Inspection for all customers, and Opportunity Inspection and Forecast for many customers. The Clari engineering team is actively working on the issue and will provide regular updates.

Starting at approximately 15:45 UTC on 2025-05-09 the processing of approximately 10% of Copilot recordings was delayed up to 4 hours. This was caused by a heavy call volume creating resource contention. The incident was resolved by expanding our cloud processing capacity resulting in all recordings being processed and available by 20:56 UTC the same day. No customer or call data was lost.

Issue is resolved.

Some copilot customers with high call volumes may have seen delays of up to 4 hours before their recordings became available. This issue is now resolved.

Around 2025-04-07 16:00 UTC, our monitoring systems flagged increased error activity related to Google Meet recordings. Upon investigation, we determined that these were false alerts, triggered by a recent change in Google Meet’s behavior that treated Clari Copilot being denied entry into meetings as failures.The alerts were cleared and the incident was resolved by 19:16 UTC on the same day. All Google Meet calls during this period were recorded as expected, and no user data was at risk.

After investigation, we've determined this was a false alarm triggered by internal monitoring. There is no impact to customer recordings, and all services are functioning as expected. A summary of the incident will be posted within the next three US business days.

Google Meet recordings are experiencing higher than expected error rates. Our engineering team is actively investigating.

On April 4, 2025, at 11:00 UTC, OmniDialer users experienced call failures and received the error message, "We are sorry, an error has occurred." This issue prevented users from successfully initiating calls through the Dialer application. The Clari Engineering team promptly investigated the incident and identified a recent code change as the root cause. This change was rolled back and the issue was resolved at 12:33 UTC on the same day.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

Our engineering teams have identified the issue and are implementing a fix.

Dialer service is currently unavailable. Our engineering team is actively investigating.

On April 7, 2025, at 20:35 UTC, Groove Scheduler experienced intermittent availability due to an increase in traffic. Our engineering team promptly implemented the necessary adjustments to accommodate the surge. Service was fully restored by 20:48 UTC.  At no time during this incident was user data at risk.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

We are continuing to monitor for any further issues.

Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

Some customers may be seeing problems with using Groove Scheduler for Groove Extension and Groove Outlook Add-In. Our engineering team is actively investigating.

At 20:30 UTC on March 25 2025, Clari Copilot stopped sending email notifications to users due to email quota getting exhausted. During this time, emails for Clari Copilot that should have been sent out could not be delivered and were lost due to this outage. As of 17:47 UTC March 26 2025, this limit has been increased to prevent the issue from reoccurring. At no time during this incident was user data at risk.

Users should be receiving emails now. Issue has been resolved.

The team is actively working on fixing the issue.

Copilot users will not be receiving invite, forgot password, and meeting reminder emails.

At 07:44 UTC on March 21, 2025, a change to a key database caused queries to be executed inefficiently when retrieving certain data. This caused APIs serving the Clari AI Projection to time out which resulted in the Trend Analytics module being unavailable and the AI Projection in Pulse Analytics not loading. To resolve this issue we created a set of new indexes on this database to improve performance, with normal operations restored by 18:12 UTC. At no time during this incident was user data at risk.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

Our engineering teams have identified the issue and are implementing a fix. Trend is not available for many customers and unable to use AI projections in Trend and Pulse. The next status update will be after the fix has been applied.

Our engineering teams have identified the issue and are implementing a fix. Many customers are unable to use AI projections in Analytics Pulse and Trend The next status update will be after the fix has been applied.

Some customers may be seeing problems with fetching AI predictions in Analytics Pulse view. Our engineering team is actively investigating.

At 14:00 UTC on March 19, 2025, a traffic surge overwhelmed one of our key databases due to an inefficient query being executed under certain conditions. This caused disruptions to our login service, preventing many users from accessing their accounts, between 14:06 and 14:59 UTC. To resolve the issue, we increased database capacity and cleared the backlog of pending queries. By 15:00 UTC, normal operations were fully restored. At no time during this incident was user data at risk.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

The Clari Revenue platform is currently unavailable for all users. Our engineering team is actively investigating the issue.

On March 7, 2025, at 13:02 UTC, a deadlock in the RevDB database caused the Clari Revenue Platform to become unresponsive, resulting in increased latency and errors. The Engineering team identified the issue and resolved it by 16:30 UTC the same day. Preventative measures have been implemented to avoid future occurrences. No customer data was compromised during the incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

The Clari Revenue platform is currently unavailable for most of our customers. Our engineering team is actively investigating the issue.

On February 17, 2025, Microsoft began the deprecation of their legacy Outlook authentication, preventing applications relying on this method from reconnecting. Starting February 25, 2025, organizations that had already received the authentication update from Microsoft could no longer authenticate with the Clari Groove Outlook Add-In. The Clari Groove Engineering team promptly resolved the issue by updating the authentication method. This change was rolled out on March 03, 2025 at 16:00 UTC. No customer data was compromised during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

We are following up with an update on the recent changes rolled out by Microsoft that impacted how Outlook connects with third-party applications like Clari Groove. We have successfully implemented a solution and rolled it out to all Outlook users. The update changes how we authenticate to Outlook to be more secure and compliant with their changes. Additionally, it will re-enable the usage of the Clari Groove add-in in Outlook if you were impacted by Microsoft’s change, or prevent you from experiencing it if you have not yet been impacted. What You Need to Do Now For Outlook web users: 1. Refresh your browser tab 2. Open up the Clari Groove add-in and log back in For Outlook desktop users: 1. Close and reopen the Outlook application 2. Open up the Clari Groove add-in and log back in Looking Ahead We sincerely apologize again for the disruption. We're improving how we receive and respond to critical Microsoft updates to act earlier and minimize future disruptions. If you have any questions, please reach out to support. Thank you, Clari Product Team

We are following up with an update on the recent changes rolled out by Microsoft that impacted how Outlook connects with third-party applications like Clari Groove. We’re continuing to test our fix and make sure that it doesn’t have any negative impacts on Clari Groove functionality. We intend to release the fix as soon as we are able to safely do so, at which point all impacted users should no longer experience a connection issue. We will follow up with an additional update early next week. If you have any questions, please reach out to support. Thank you, Clari Product Team

Microsoft recently rolled out changes to how Outlook connects with third-party applications like Clari Groove. As part of their Secure Future Initiative, Microsoft is turning off Legacy Exchange identity tokens, which will disrupt your Groove and Outlook connection. Some customers have already experienced issues, and we expect this change to continue impacting all users. What We’re Doing We’re actively implementing a long-term solution that aligns with Microsoft’s new infrastructure. Once that’s in place, no further action will be required from you. We’ll provide an update on our progress by Friday, February 28. What You Need to Do Now To prevent or resolve any disruptions, your IT Admin will need to temporarily re-enable legacy tokens by following Microsoft’s instructions: Install PowerShell on Mac/Linux/Windows: https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-macos?view=powershell-7.5 Install the Exchange Online PowerShell module: https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#install-and-maintain-the-exchange-online-powershell-module Turn on legacy exchange online tokens: https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/turn-exchange-tokens-on-off#turn-on-legacy-exchange-online-tokens ⚠️ It can take up to 24 hours for Outlook add-ins to function normally after making these changes. Looking Ahead We understand how critical Groove is to your team, and we sincerely apologize for the disruption. While Microsoft communicated this change through standard channels, it wasn’t surfaced in a way that clearly signaled its impact. We’re working directly with Microsoft to improve how these updates are communicated so we can act earlier and minimize disruptions in the future. If you have any questions, please reach out to support. Thank you, Clari Product Team

On February 17, 2025 Microsoft started rolling out changes to the Legacy Exchange user identity tokens and callback tokens. These tokens will be turned off by default for all Exchange Online tenants as part of Microsoft’s Secure Future Initiative. This will impact your ability to connect Microsoft Outlook to Clari Groove and will impact all Outlook users as Microsoft rolls out this update. In the interim to mitigate this change, the IT Admin at your organization will need to follow Microsoft’s instructions to prevent the legacy tokens from being deprecated. This will prevent your organization from experiencing connection issues between Microsoft Outlook to Clari Groove. Install PowerShell on Mac/Linux/Windows: https://learn.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-macos?view=powershell-7.5 Install the Exchange Online PowerShell module: https://learn.microsoft.com/en-us/powershell/exchange/exchange-online-powershell-v2?view=exchange-ps#install-and-maintain-the-exchange-online-powershell-module Turn on legacy exchange online tokens: https://learn.microsoft.com/en-us/office/dev/add-ins/outlook/turn-exchange-tokens-on-off#turn-on-legacy-exchange-online-tokens It can take up to 24 hours before all requests from Outlook add-ins for legacy tokens are allowed. We are actively working on supporting the new infrastructure. After implementing the interim change, no further updates will be required by your IT Admin at that time. Related links: https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#exchange-user-identity-token https://learn.microsoft.com/office/dev/add-ins/outlook/authentication#callback-tokens https://blogs.microsoft.com/on-the-issues/2023/11/02/secure-future-initiative-sfi-cybersecurity-cyberattacks/

We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.

We are currently investigating this issue.

We have confirmed the issue has been resolved for the impacted users.

Groove is currently experiencing issues, and the Engineering team is actively investigating. In the meantime, we recommend users log out and log back in to continue using it.

Groove is experiencing system availability issues and users might experience intermittent login issues. While the team is actively investigating advice users to log back in to continue working.

Starting February 14, 2025 22:51 UTC, users intermittently experienced issues in the “Opportunities” module, when grouping by the “Owner” field. The Clari Engineering team resolved the issue by restarting the service on February 19, 00:28 UTC. No customer data was compromised during this incident.

The team has now fixed the issue.

The team is actively applying a fix to resolve the issue

There are intermittent issues with the Opportunities module while attempting to Group By an owner field.

On February 18, 2025 11:30 UTC, Clari copilot encountered delays in transcription availability for dialler calls due to an issue with our call transcription model. The Clari engineering team resolved this issue by 12:52 UTC, restoring transcription for all affected dialer calls. No customer data was compromised during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Some customers may be seeing problems with their Dialler calls in Clari Copilot. Our engineering team is actively investigating.

On February 13, 2025 02:28 UTC, a code change resulted in a failure to deliver emails. The issue was identified later the same day, and a fix was deployed. All affected emails were reprocessed and successfully delivered. No user data was impacted during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix as well as resending all missed emails.

The issue has been identified and a fix is being implemented.

Our engineering team is actively investigating.

At 2025-02-10 10:00 UTC a background system change caused the Copilot recorder to stop joining previously scheduled meetings \(calls\). Approximately 1000 meetings were missed before the issue was identified and fixed at approximately 16:10 UTC. Only manually invited meetings were recorded during this time period. No other Copilot functionality was affected by this incident.

We have identified and fixed the issue. Recorders should now join the meetings as expected

Between 11:00 UTC and 16:30 UTC an automation that triggers a flow of recorder bots joining scheduled calls was not working as expected, which resulted in multiple scheduled meetings not to have a recorder present. We have identified and fixed the problem and are now monitoring the fix

On 2025-01-16 16:18 UTC, Clari Copilot WebApp users encountered intermittent issues due to high latencies. This was due to a deployment of new code. Our monitoring identified the intermittent issue and we reversed the deployment. By 17:26 UTC, the issue was resolved. No customer data was compromised during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Copilot login problems were experienced by customers from 2025-01-16 16:18  to 17:26 UTC. The problem is resolved at the time of publishing this announcement.

On 2025-01-12 and 13, Groove WebApp, Extension, Dialer and Outlook Add-In users encountered sporadic issues logging into LinkedIn through Groove. This was due to an API problem at LinkedIn reported as [https://www.linkedin-apistatus.com/incidents/fk1wj964rzts](https://www.linkedin-apistatus.com/incidents/fk1wj964rzts) . By 2025-01-13 21:00 UTC, we were able to confirm the issue had been resolved. No customer data was compromised during this incident.

We have confirmed the issue has been resolved for the impacted users as of 21:01 UTC. A summary of the incident will be posted within the next three US business days.

LinkedIn has validated an ongoing issue with LinkedIn AccessToken and Authorization API https://www.linkedin-apistatus.com/. We're monitoring their resolution progress to validate functionality of LinkedIn Sales Navigator within Groove.

Our monitoring is showing the connection issues have abated. Access to LinkedIn Sales Navigator is now functional.

Some customers may be seeing problems with LinkedIn login via Groove WebApp, Actions or Ominibar. Our engineering team is actively investigating the issue.

On 2025-01-06 at 12:34 UTC, users of the Groove WebApp, Extension, Dialer, and Outlook Add-In experienced login issues due to an expired SSL certificate. The expiration occurred during the holidays and was missed in our standard notification processes. By 01:35 UTC, the engineering team resolved the issue, and users are advised to perform a hard refresh on their browser to ensure normal functionality. No customer data was compromised during this incident. We recognize that this issue was preventable and have implemented stricter site validation measures to ensure similar incidents do not happen in the future.

On 2025-01-06 12:34:00 AM UTC, Groove WebApp, Extension, Dialer and Outlook Add-In users encountered issues with the login into Groove. As of 01:35:00 AM UTC engineering team has fully resolved the issue and users are advised to hard refresh the browser to ensure the app works normally. No customer data was compromised during this incident

On 2025-01-06 12:34:00 AM UTC, Groove WebApp, Extension, Dialer and Outlook Add-In users encountered issues with the login into Groove. As of 01:35:00 AM UTC engineering team has fully resolved the issue and users are advised to hard refresh the browser to ensure the app works normally. No customer data was compromised during this incident.

The issue has been identified and a fix is being implemented.

On 2024-12-5 21:30 UTC, an infrastructure update prevented customers’ custom domains from reaching Groove Clari servers. The problem was fixed on 2024-12-9 17:20 UTC. No customer data was impacted during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

We are currently investigating this issue.

On 2024-12-13 18:00:00 UTC, some Groove Outlook Add-In users encountered intermittent issues with the 'Send with Groove' feature in the Outlook ribbon. By 2024-12-13 19:55:00 UTC, a workaround was provided: users can send emails via Groove by using the 'Send with Groove' button available within the Groove Outlook Add-In.  ‌ On 2024-12-18 21:50:00 UTC, we released an updated version of the Groove Outlook Add-In with enhanced logging capabilities to help identify a permanent fix. In the meantime, users are advised to continue using the workaround. No customer data was compromised during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

Our engineering teams have identified the issue and are implementing a fix. Users who are sending mail through Outlook with Groove may be having some messages delayed. The next status update will be after the fix has been applied.

We are currently investigating this issue.

On 2024-12-01 approximately 14:00 UTC, Clari detected that RevDB data was delayed for many customers. RevDB data caught up for all customers by 2024-12-03 2:30 UTC.

This incident has been resolved.

Our engineering teams have resolved the issue and we are monitoring the fix.

We are making progress in the investigation. Some customer are now fully restored, and we are working on restoring the data freshness on the remainder of the customers.

We're currently investigating the issue, and will provide an update soon.

We're currently investigating the issue, and will provide an update soon.

On 2024-12-07 11:00 UTC, Clari began experiencing elevated latency, leading to slow or degraded performance for some customers in the opportunities and forecasting modules. By 2024-12-07 12:50 UTC the system recovered, and the incident was resolved at 2024-12-07 13:17 UTC.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

Some customers may see degraded performance. We're currently investigating the issue, and will provide an update soon. Our engineering team is actively investigating.

Starting at 2024-12-5 18:11 UTC, a change was introduced to Clari’s Inspect module that resulted in several customers unable to access the Opportunity Grid within Clari. The problematic change was rolled back at 20:50 UTC. We confirmed that the issue was resolved for all impacted customers by 21:15 UTC. No customer data was at risk during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

Several customers have reported difficulty accessing the Opportunity Grid within Clari. Our Engineering team is actively investigating this issue.

Starting on 2024-11-22 10:27 UTC a change was introduced to the Copilot Smart Summary service that resulted in the service being unable to process requests and generate summaries. This issue was fixed at 13:47 UTC and the backlog of pending transcripts was resolved by 16:26 UTC the same day.

We have confirmed that all delayed summaries have been processed. A summary of the incident will be posted within the next three US business days.

The engineering team has identified and fixed a bug in smart summaries generation pipeline. We are currently monitoring the queue of unprocessed summaries and will provide an update when the issue is fully resolved

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have identified the issue and are implementing a fix. The next status update will be after the fix has been applied.

Our engineering team is actively investigating a delay in Forecasting that may result in some customers seeing stale data.

Between 2024-11-21 15:20 – 15:26 UTC, the Clari platform had slow responses and increased errors due to a back-end database problem that slowed down one of our core services. Automatic scaling to increase the capacity of the core service restored normal performance as the backlog to the database was reduced. No user data was at risk during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

We have noticed an increased latency and error rate for Clari Revenue Platform. Our engineering team is actively investigating.

Clari engineering detected a spike in errors when connecting to Salesforce, which turned out to be a Salesforce incident \(see: [https://status.salesforce.com/incidents/13457](https://status.salesforce.com/incidents/13457)\), which we monitored through it to its resolution.

Based on our data and Salesforce status updates (https://status.salesforce.com/incidents/13457) we believe that the incident is now resolved

Due to partial Service Disruptions at Salesforce (https://status.salesforce.com/incidents/13457) we are observing a higher error rate on a subset of functionalities. Our engineering team is monitoring the situation closely. We will publish an update once the incident is resolved and we confirm that functionalities depending on Salesforce are fully restored

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Multiple organizations have reported errors when attempting to send email via Groove. Our engineering team is actively investigating.

Starting on 2024-11-15 11:00 AM UTC, users relying on the "Send with Groove" feature in Outlook Add-in experienced delays in sending out emails. Our team monitored the situation and implemented measures to restore normal service by 2024-11-15 8:15 PM UTC. We understand the importance of timely email communication and apologize for any inconvenience this may have caused. No user data was at risk or damaged by this incident.

The issue has been resolved.

New emails Send With Groove functionality in Outlook Add-in might take up to 20 minutes to be delivered.

We're currently experiencing a degradation of Send With Groove functionality in Outlook Add-in. Emails to be sent out are processing through our queues at a slower pace than normal.

On November 12, 2024 at 7:14 PM UTC, Google released an update to their Chrome Browser \(version 131\) that was found to be incompatible with a dependency that Groove uses for HTTP requests. This caused a temporary disruption impacting the Groove Webapp, Groove Chrome Extension, and Groove Outlook Add-in Webapp. The Groove Outlook Add-in Desktop app remained unaffected. **Resolution**  On November 13, 2024 at 1:22 AM UTC, the issue was addressed by updating the identified conflicting dependency. This update restored functionality for the Groove Webapp and Groove Outlook Add-in Webapp. No user data was at risk or damaged by this incident.  **Next Steps for Chrome Extension Users** For Groove Chrome Extension users, we request that you update to the latest version \(2024.11.12.35033\) to ensure full functionality. The publication of this version was first made available on November 13, 2024 at 7:08 AM UTC. Please check your browser extension settings or contact support if assistance is needed. We apologize for any inconvenience caused and appreciate your patience during this time. Thank you for your continued support.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days. For users using the Groove Chrome Extension and are still experiencing the issue, please update to the version: 2024.11.12.35033.

We have resolved the issue for the Groove Webapp. We have submitted a fix to the Chrome Extension Webstore and are awaiting approval of the fix. If you’re still seeing problems within Groove Extension, it may take up to 48 hours to receive the latest Groove Extension version. We will provide an update once the extension is published.

We are continuing to work on a fix for this issue.

We’re investigating an issue with the Groove Chrome Extension, Dialer, and Web App where users are having issues connecting Salesforce. We have narrowed the root cause to the latest Chrome version that was released today and do not recommend customers upgrade to version 131 at this time. Our team is actively working on a fix.

We are currently experiencing an issue where users are unable to authenticate to Salesforce. Users may see a white screen when being redirected to the Salesforce Login page and/or unable to sign in. Our engineering team is actively investigating.

Starting on 2024-10-29 at 09:40 UTC, some customers reported missing email and meeting bodies for the users. Clari’s Engineering team investigated this and identified that the email and meeting bodies were missing until 2024-10-23 02:30 UTC for a few customers. This was caused by an error that unintentionally deleted Clari’s copy of the emails and meetings for these users. A fix was implemented at 15:40 UTC that same day, and all missing email and meeting content for affected users was fully restored by 2024-10-31 at 05:30 UTC. No user data was at risk or damaged by this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and are actively monitoring the fix. Meeting bodies have been partially recovered for impacted users, and we are closely tracking the ongoing recovery progress.

Our engineering teams have implemented a fix. Email bodies are now available. The next status update will be when remediation efforts are complete for meeting bodies as well.

Some users are currently experiencing an issue where email and meeting bodies in Accounts and Opportunities are only available from October 23 14:00 UTC, with data for certain users potentially appearing from an even later date. Our engineering team has identified the issue and is working on a fix.

On 2024-09-04 at approximately 19:00 UTC, Clari enabled a feature to translate Salesforce-defined formula fields to Clari. A misconfiguration caused some fields not to display in Clari for some users. Clari immediately focused on resolving this issue, which was fully resolved at 2024-09-06 5:00 UTC. This issue impacted 20 customers. No customer data was at risk during this incident.

Clari engineering has confirmed that all affected customers have been fully resotred. The root cause has been identified and an RCA will be published within 3 business days.

Access has been restored to affected customers. The Clari engineering team will continue to monitor for any additional issues.

Starting at approximately 17:00 UTC on September 4, a small number of customers began experiencing errors when loading opportunity records from RevDB, which could impact Opportunity Inspection, Dashboards and other views. The root cause has been identified and the engineering team is actively working on restoring access to all customers. The issue involves certain fields, which map to formula fields in Salesforce, became unavailable while dependent data was loaded from Salesforce. Some customers will see service restored automatically as the new data is loaded and processed, but the Clari team is working to mitigate and restore access to all customers as soon as possible.

Some customers may be seeing problems with accessing opportunity lists in the Clari web app Our engineering team is actively investigating.

On October 25, 2024 at 3:39 UTC, Clari performed a scheduled release of Clari Forecast. Changes to configuration in this release caused degraded performance starting at approximately 15:07 UTC. Clari immediately focused on resolving this issue. A rollback was initiated and completed by 15:47 UTC, at which point functionality was fully restored. No customer data was at risk during this incident.

This issue has been resolved.

We have resolved the issue and our engineering team is continuing to monitor.

We've identified the problem and our engineering team are working on a fix.

Clari Forecast is experiencing issues or unavailable for some customers. Our engineering team is investigating and will provide an update soon

On October 24th, 2024, from 17:30 UTC to 23:30 UTC, some customers experienced issues logging into LinkedIn within Groove Actions. The team has resolved the issue, and a new extension version, 2024.10.24.22117, is now available. There was no risk to data during this incident.

This is now resolved for the majority of our customers. If you’re still seeing problems, it may take up to 48 hours to receive the latest Groove Extension version.

We have identified the issue, we are pushing a patch to remediate it. For the current affected users, please use the recommended suggestion of logging via the Omnibar and refresh the page.

We are continuing to investigate this issue.

Some Groove customers have reported difficulty using features that rely on LinkedIn integration, including sending LinkedIn messages, accessing LinkedIn profiles and authenticating. Our Engineering team is actively investigating the issue. As a workaround, users can login via the Omnibar and refresh the page.

On October 22, 2024, at 17:11 UTC, Clari initiated its scheduled product release process. During the release, an incorrect database changeset was deployed, which prevented users from logging into the Clari platform. This issue also potentially affected some users trying to access Copilot and Groove. The root cause was identified at 18:10 UTC, and a rollback of the faulty changeset was implemented and deployed by 18:18 UTC, fully resolving the issue. There was no risk or compromise to user data throughout this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have identified the issue with users not being able to access the Clari Platform. The next status update will be after the fix has been applied.

The Clari Revenue platform is currently unavailable for all users. Some users may also experience difficulties accessing Copilot and Groove. Our engineering team is actively investigating the issue.

The Clari Revenue platform is currently unavailable for all users. Our engineering team is actively investigating the issue.

On October 11, 2024, at 18:30 UTC, Groove applications encountered intermittent problems due to a database deadlock. This situation arose when multiple transactions attempted to access the same resource, causing them to become stuck. Consequently, the system stalled, and incoming requests were blocked as they awaited the completion of the deadlocked transactions. To address this, we implemented a timeout for database operations, which terminated blocked transactions after a specified duration. The issue was completely resolved by 20:03 UTC that same day. There was no risk or compromise to user data during this incident.

We have confirmed the issue has been resolved for the impacted customers. A summary of the incident will be posted within the next three US business days.

A fix has been implemented and we are monitoring the results.

We are currently investigating this issue.

On 2024-10-08 at 02:20 UTC, customers reported missing calls from Copilot. Upon investigation, Clari’s Engineering team determined that the issue began on 2024-10-07 at 04:00 UTC. The trigger was a process which accidentally deleted index references to calls beyond its intended scope of deletion. The call data itself was not impacted, only the ability to display the calls on the webpage. The missing calls were fully restored by 2024-10-09 at 02:30 UTC. No user data was at risk or compromised during this incident.

We have confirmed the issue has been resolved for the impacted customers. A summary of the incident will be posted within the next three US business days.

Restoration of call search records is taking longer than we initially estimated. We expect it to complete in 15 hours. Until it completes, some call search records might be unavailable.

Call recording search record restoration is in progress and has been completed for some customers. We expect all call search records to be restored within the next 10 hours.

Our engineering teams have identified an issue related to searching call recordings and are implementing a fix. The next status update will be after the call search fix has been applied.

There are reports of missing Copilot calls. Our engineering team is actively investigating.

On 2024-10-01 02:40 UTC, Salesforce published a degraded status notice \([https://status.salesforce.com/incidents/13231](https://status.salesforce.com/incidents/13231)\) relating to a single instance of their platform. Over the following hours, the scope of the notice was expanded to include additional platform instances. Across all of our customers, the Clari platform registered higher than normal errors reaching Salesforce from around 12:00 UTC through 21:00 UTC on 2024-10-02. Salesforce reported that their issue was resolved as of 2024-10-02 04:31 UTC. The Clari platform is now working as expected.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Salesforce core services are operational. We will continue to closely monitor performance on the Clari side to ensure smooth operations. Affected instances can be seen on this Salesforce status page: https://status.salesforce.com/products/Salesforce_Services

Salesforce continues to experience performance degradation, which is resulting in intermittent issues affecting Clari. We are closely monitoring the situation and will provide updates as they become available. Affected instances can be seen on this Salesforce status page: https://status.salesforce.com/products/Salesforce_Services

Clari is currently experiencing an outage to a subset of organizations that are on a Salesforce instance that is affected by their service disruption. Our team is actively monitoring the situation and will provide updates as they become available. Users may see errors upon logging into Clari. Affected instances can be seen on this Salesforce status page: https://status.salesforce.com/products/Salesforce_Services

Clari is currently experiencing an outage due to an ongoing Salesforce service disruption. Our team is actively monitoring the situation and will provide updates as they become available.

On 2024-10-02 19:01 UTC, the forecast module of the Clari platform was moved to a new internal hosting platform. The abrupt influx of traffic caused some customers to receive errors from this module. Clari reverted the change, and by 2024-10-02 19:25 UTC, the forecast module was successfully running on the original platform. While no user data was at risk during this issue, all failed requests during this time period will have to be re-done.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

During an internal migration, the forecasting module within Clari was over-capacity, resulting in failures for some customers. This update is being posted after the incident for customer awareness and will be moved to resolved status in a few minutes.

Starting on 2024-09-24 13:38 UTC, Clari’s Engineering team detected delays in Copilot call availability for sharing, with some calls experiencing delays of up to 10 hours. The root cause was a misconfiguration in our infrastructure, which prevented the processing pipelines from scaling to meet increased demand.  A fix was implemented at 2024-09-24 16:44 UTC, and all calls were successfully processed shortly thereafter. No user data was at risk or damaged by this incident.

We have confirmed the issue has been resolved. A summary of the incident will be posted within the next three US business days.

We have identified that Copilot users are experiencing delays in sharing calls. Our engineering team has implemented a fix. We are now working to remediate the remaining effects of the incident.

Starting around 2024-09-23 19:30 UTC, the Groove Engineering team identified performance degradation across various features of the web application. This issue was traced to a recent configuration change. The team promptly reverted the configuration at around 2024-09-23 23:00 UTC, and full functionality was restored shortly thereafter. In addition, we have enhanced our monitoring and alerting systems to prevent a recurrence of this issue.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue and we are monitoring the fix.

Customers who are using Groove Flows and Actions may experience intermittent errors while executing or accessing Actions or certain sub pages within Flows. Team is actively investigating the incident.

Starting on 2024-09-26 at 01:45 UTC, a configuration change caused an unexpected side effect of the Analyze module not loading for a subset of customers.  A configuration fix was released to address the issue at around 2024-09-26 11:49 UTC, and the Analyze module was operational shortly after. No user data was at risk during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have identified the issue and are implementing a fix. Customers might not be able to load the Analyze module. The next status update will be after the fix has been applied.

Some customers may be seeing problems with Analyze. Our engineering team is actively investigating.

Some customers may be seeing problems with Analyze. Our engineering team is actively investigating.

Some customers may be seeing problems with Analyze. Our engineering team is actively investigating.

Some customers may be seeing problems with Analyze. Our engineering team is actively investigating.

The incident has been resolved. We have identified the problem to be a new navigation bar that was rolled out recently. We have restored the original navigation bar and the Capture tab should show up for all users.

The module itself is working for all the users. The capture tab isn't visible in the UI but navigating to the actual URL http://app.clari.com/autocapture works.

AutoCapture module is down for multiple customers. The RCA is unknown and the team is still investigating the cause

Starting on 2024-09-18 at 04:40 UTC, Clari’s Engineering team identified delays in Capture’s writing back Activity and Contacts to Salesforce \(SFDC\), with some delayed by up to 10 hours. A fix was implemented at 05:58 UTC the same day, and all writebacks were successfully processed shortly thereafter. No user data was at risk or damaged by this incident.

We have confirmed the issue has been resolved for the impacted customers. A summary of the incident will be posted within the next three US business days.

Our engineering teams have resolved the issue, and the Capture product is now functioning as expected, with all new updates being synced to Salesforce. We are currently processing the pending data for affected customers and will provide an update once this process is complete.

We have identified that the writeback of Contacts and Activities to SFDC has not been functioning since September 17th, 20:00 UTC. Our engineering teams have identified the issue and are implementing a fix.

Starting around 2024-09-13 23:30 UTC, Clari’s Engineering team noticed delays in RevDB data processing, which delayed data loading into various modules such as Analytics, Accounts, Opportunities, and Forecasting for up to 3.5 hours. A fix to handle this scenario was made around 2024-09-14 03:20 UTC, and all data processing pipelines caught up shortly thereafter. No user data was at risk or damaged by this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. RevDB data is still delayed but started to catch up. The engineering team is actively monitoring the status of the issue. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

Our engineering teams have identified the issue and are implementing a fix. The next status update will be after the fix has been applied.

Clari has detected delays in processing RevDB data and the engineering team is investigating. Modules running on RevDB will see delays in data loading; this will include Analytics, Accounts and for some customer also Opportunities and Forecasting.

Starting around 2024-09-09 22:51 UTC, a release caused an unexpected side effect of Groove Dialer users receiving error messages upon executing Call Actions. This impacted dialer customers using the new Action Compose feature. After discovering the problem through an internal monitoring tool, a code fix was released to address the problematic code area at around 2024-09-10 16:22 UTC. The Action Compose feature now works as expected.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Customers trying to execute Call Actions with Groove Dialer may have received an error message upon completing a Call Action. We have fixed the problem. Please refresh the Groove Web App browser tab(s) if you are still experiencing the problem.

On 2024-09-05 starting around 01:00 UTC, Clari \(Capture\) encountered an issue that temporarily halted the processing of contacts and activities to Salesforce due to an incorrect version in the deployment. The issue was identified and resolved by re-deploying the affected module, and all impacted contacts and activities were successfully re-processed. The incident was fully resolved by 09:00 UTC on the same day. No data was at risk during this incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have implemented a fix. We are now working to remediate the remaining effects of the incident. The next status update will be when remediation efforts are complete or the state of this incident otherwise changes.

Our engineering teams have identified the issue and are implementing a fix. The next status update will be after the fix has been applied.

Capture is not working as expected and some customers may not see latest contacts and/or Activities written to their CRM systems from Clari. Our engineering team is actively investigating.

On 2024-09-05 around 04:30 UTC, Clari's User Management module started to incorrectly display users as "Not Registered" for about 3% of customers due to an incorrect configuration change. The issue was resolved at 2024-09-05 16:22 UTC after fixing the relevant configuration. No data loss resulted from the incident.

We have confirmed the issue has been resolved for the impacted users. A summary of the incident will be posted within the next three US business days.

Our engineering teams have identified the issue and are implementing a fix. The next status update will be after the fix has been applied.

Multiple customers are reporting a problem provisioning new users for forecasting. Our engineering team is actively investigating.