57 Clari incidents · février 2025 — official updates, affected components, duration and resolution details.
Nous enquêtons actuellement sur cette question.
Nous avons confirmé que le problème a été résolu pour les utilisateurs touchés. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous avons reçu des clients des rapports indiquant que leur utilisateur d'intégration Salesforce est déconnecté en raison de l'expiration du jeton. Notre équipe d'ingénieurs enquête activement.
Un petit nombre de clients ont déconnecté leur utilisateur d'intégration Salesforce en raison de l'expiration du jeton. Lorsque cela se produit, la synchronisation régulière des données dans Clari est incapable d'exécuter. Notre équipe d'ingénierie et le soutien de Salesforce enquêtent sur le problème. Aucune nouvelle déconnexion n'a été observée depuis 2026-08-16. Si votre utilisateur d'intégration a été déconnecté, vous pouvez le reconnecter pour résoudre le problème de synchronisation. Si vous avez besoin d'aide, veuillez communiquer avec Support pour obtenir de l'aide.
Le problème semble avoir été un événement unique avec Salesforce. Nous continuons à surveiller toute récurrence et sommes activement engagés avec le soutien de Salesforce pour comprendre ce qui s'est passé et comment éviter d'autres événements. Nous laisserons ce dossier dans un état de « surveillance » jusqu'à ce que nous ayons une compréhension satisfaisante de l'incident, mais ne nous attendons pas à faire d'autres mises à jour.
Nous avons confirmé de Salesforce ce qui a causé la panne pour les utilisateurs touchés. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
Le 2026-08-16, une migration de Salesforce Hyperforce a causé des interruptions de connexion entre Salesforce et Clary sur un petit groupe de comptes clients. Ce numéro a temporairement interrompu les mises à jour de données automatisées pour certaines organisations et a demandé à leurs utilisateurs d'authentifier avec Salesforce. Il n'y a pas de moyen connu d'éviter cette situation pour les futures migrations Hyperforce, mais nous continuons à travailler avec Salesforce pour explorer des options.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nos équipes d'ingénierie ont identifié le problème et mettent en place une solution. Certaines ou toutes les pages ne sont pas chargées. La prochaine mise à jour du statut sera après l'application de la correction.
Nos équipes d'ingénierie ont identifié le problème et mettent en place une solution. Certaines ou toutes les pages ne sont pas chargées La prochaine mise à jour du statut sera après l'application de la correction.
Le problème sous-jacent a été corrigé, nous surveillons pour nous assurer que toutes les fonctionnalités sont rétablies.
Nous restons à l'affût de tout autre problème.
Nous avons confirmé que le problème a été résolu pour les utilisateurs touchés. Aucune nouvelle erreur n'a été observée au cours des 60 dernières minutes de surveillance. Toutes les composantes touchées sont pleinement opérationnelles maintenant. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
À environ 2026-08-05 00:02 UTC, un sous-ensemble d'organisations a connu des erreurs lorsqu'elles ont tenté d'accéder à l'application Clary. Les utilisateurs touchés ont vu le message : « Quelque chose a mal tourné avec le chargement des ressources de l'application. » Notre équipe d'ingénieurs a identifié une régression introduite lors d'un déploiement récent et a émis un hotfix. Systèmes retournés aux opérations normales à 2026-08-05 13:30 UTC . Aucune donnée client n'était en danger à aucun moment durant cet incident.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Nous enquêtons actuellement sur les rapports de problèmes d'accès intermittents avec la plateforme Clary. Les clients peuvent éprouver des difficultés à accéder à l'application ou rencontrer des performances lentes. Notre équipe d'ingénieurs travaille activement à résoudre ce problème. Nous fournirons des mises à jour à mesure que de plus amples renseignements seront disponibles.
Nos équipes d'ingénierie ont résolu le problème et la performance du système est de retour à la normale. Nous continuons de surveiller la solution.
Après avoir suivi le problème pendant 3 heures, nous n'avons pas vu de récurrences et la plateforme a été stable. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
Vers 2026-07-27 13:15 UTC certains utilisateurs ont connu des temps de chargement et des erreurs de longue durée en essayant d'utiliser l'application Clary. L'équipe d'ingénierie a pu déterminer qu'un problème lié à l'échelle de certains de nos services basés sur le cloud était la source du problème et a déployé une correction pour restaurer les performances du système. Les systèmes sont revenus à des opérations normales à partir de 2026-07-27 15:30 UTC et aucune donnée client n'était à risque pendant la panne.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Certains clients peuvent éprouver des problèmes avec les enregistrements d'appels Clari Copilot dans Zoom. Notre équipe d'ingénieurs enquête activement.
Notre équipe d'ingénieurs enquête toujours activement. Le problème est d'influencer les clients en s'appuyant sur des enregistreurs Web pour les enregistrements Zoom. Nous fournirons une autre mise à jour dès que plus d'informations seront disponibles.
Les clients touchés continuent de voir des problèmes avec les enregistreurs Web sur Zoom. Notre équipe d'ingénierie étudie activement avec le support Zoom et examine les chemins alternatifs pour les clients touchés de reprendre la fonctionnalité d'enregistrement. Nous fournirons une autre mise à jour dès que plus d'informations seront disponibles.
La question est toujours à l'étude. Les clients touchés continuent à éprouver des problèmes avec les enregistreurs Web sur Zoom. Notre enquête indique que les changements récents dans le comportement de la plate-forme de Zoom-Stop empêchent certains enregistreurs de rejoindre les réunions des clients. Notre équipe d'ingénierie travaille activement avec Zoom Support pour résoudre le problème. Nous fournirons une autre mise à jour dès que plus d'information sera disponible.
Nos équipes d'ingénierie ont identifié le problème et mettent en place une solution.
Nous avons publié des conseils sur l'application enjoignant aux clients touchés de reconnecter leur intégration Zoom dans Clari Copilot, ce qui permet aux clients de restaurer la capacité de Copilot d'enregistrer des réunions Zoom.
Nous avons travaillé avec Zoom pour résoudre le problème touchant les enregistreurs Web. Les enregistrements fonctionnent maintenant comme prévu. Notre équipe d'ingénierie surveille le système, et nous fournirons une autre mise à jour si quelque chose change. Pour les clients touchés, y compris ceux qui ont déjà reconnecté leur intégration Zoom, aucune autre action n'est nécessaire. Si vous rencontrez encore des problèmes, veuillez contacter notre équipe de support.
Nous avons confirmé que le problème a été résolu pour les utilisateurs touchés. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
À partir d'environ 2026-07-13 06:30 UTC, un changement dans la plate-forme de Zoom a affecté la capacité de l'enregistreur Web Zoom de Clarier Copilot de rejoindre et enregistrer des réunions. Par conséquent, certains clients n'ont pas été en mesure d'enregistrer les réunions Zoom en copilote pendant la période touchée. Ce problème n'a eu qu'une incidence sur l'enregistrement en ligne Zoom; d'autres plateformes d'enregistrement n'ont pas été touchées. Les réunions prévues pour cette période peuvent ne pas avoir été enregistrées. Lorsqu'elle a cerné la question, l'équipe d'ingénierie Clary a travaillé en étroite collaboration avec Zoom pour étudier le changement, en déterminer l'impact et mettre en oeuvre les mesures d'atténuation nécessaires. Zoom web recorder rejoints ont retourné à l'exploitation normale, et nous avons confirmé la récupération complète d'environ 2026-07-15 11:08 UTC. Nous continuons de travailler avec Zoom pour mieux comprendre le changement et renforcer notre intégration afin que des changements similaires puissent être traités avec plus de grâce à l'avenir.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Our engineering team is actively investigating.
We are observing a partial outage with Copilot recordings across all platforms. Our engineering team is actively investigating.
We identified a few changes from the Copilot Infrastructure maintenance on Saturday June 20th that caused some recorders to fail. We have fixed the issue and are continuing to monitor the system. We will provide another update end of day tomorrow before we resolve this incident.
We have identified that we are not showing the consent page during call recordings. We are working on a fix and will provide an update as soon as the issue is resolved.
We have resolved the issue that was preventing the consent page from displaying during call recordings. We are continuing to monitor the system after the Copilot Infrastructure maintenance on Saturday June 20th and we will provide another update by the end of day tomorrow before we resolve this incident.
We are continuing to monitor this issue and will leave this incident open until the end of the day. If no further issues are observed by that time, we will resolve the incident. If you are continuing to see any issues with the Copilot platform please reach out to the Clari customer support team.
After monitoring Copilot performance throughout the day and not seeing any reoccurrence of the issues the Clari Engineering team is marking this incident as resolved.
Beginning around 08:23 UTC on 2026-06-22 some Clari Copilot customers experienced failures across Zoom, Google Meet, and Microsoft Teams that prevented calls from being recorded. The errors were traced back to the Copilot maintenance on 2026-06-20 and configuration changes that were not fully applied. The Clari Engineering team remediated the issue by applying the configuration changes and validating the changes. Call recording functionality was restored at approximately 18:40 UTC 2026-06-22. We continued to monitor the system for the next 24 hours to ensure that there were no further issues before resolving the incident.
Notre équipe d'ingénierie enquête activement sur la cause profonde des trois plateformes. Nous surveillons de près les taux de réussite des appels et fournirons des mises à jour à mesure que nous en apprendrons davantage.
Nous avons confirmé que le problème a été résolu pour les utilisateurs touchés. Un résumé de l'incident sera affiché dans les trois prochains jours ouvrables américains.
À partir de 08:23 UTC sur 2026-06-22 certains clients Clari Copilot ont connu des défaillances dans Zoom, Google Meet et Microsoft Teams qui ont empêché les appels d'être enregistrés. Les erreurs ont été retracées à la maintenance de Copilot le 2026-06-20 et les modifications de configuration qui n'ont pas été entièrement appliquées. L'équipe de Clary Engineering a corrigé le problème en appliquant les modifications de configuration et en valideant les modifications. La fonctionnalité d'enregistrement des appels a été restaurée vers 18h40 UTC 2026-06-22. Nous avons continué de surveiller le système pendant les 24 prochaines heures pour nous assurer qu'il n'y avait pas d'autres problèmes avant de résoudre l'incident.
Traduit automatiquement depuis la mise à jour officielle de l'incident.
Clari is currently experiencing longer load times and errors than normal. Our engineering team is actively investigating the issue.
The engineering team is continuing to investigate the issue. At this time users may still be experiencing longer page load times or increased errors.
We have identified and fixed a problem that was overloading database queries and resulted in slow performance throughout the application. All systems should be functioning normally again.
At approximately 23:44 on 2026-06-05 UTC some Clari users experienced long page load times and errors when trying to use the application. The Clari Engineering team was able to determine that a database operation was continually executing and overloading one of the databases. Once the database call was stopped and the stuck connections were cleared, system performance was able to return to normal at around 04:33 on 2026-06-06 UTC.
Some customers may be seeing problems with connectivity to Salesforce CRM Integration. Our engineering team is actively investigating.
We are continuing to investigate this issue.
Update: Resolution Requires Customer Action Our engineering teams have resolved the issue and we are monitoring the fix. However, customers who continue to experience an impact must take action to fully restore functionality. Required Action: Salesforce Administrators (Role: Full System Administrator) must: * Navigate to **Workspace Settings > Integrations** in Clari Copilot. * Re-authenticate the Salesforce integration. Resolution Process: After re-authentication - Our systems will automatically re-sync your Salesforce data from the impacted window. - Full functionality will be restored within the following hours. Who Should Take Action: Customers who continue to experience Salesforce CRM connectivity issues after this update. If you encounter any issues or need assistance during the re-authentication process, please reach out to our Support Team.
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.
Starting at approximately 15:25 on 2026-06-04 UTC, a code defect in Clari Copilot's internal integration maintenance process caused Salesforce integrations to become disconnected for a subset of customers. This impacted Salesforce data sync only. All other Copilot functionality continued to operate normally. The Clari engineering team identified the cause and rolled out a fix at 18:29 on 2026-06-04 UTC. Affected customers were provided re-authentication instructions to restore their Salesforce connection, after which full functionality resumed. No customer data was lost during this incident
Some customers using Copilot with Google Meet are not seeing their meetings recorded. Our engineering team is actively investigating.
Our engineering teams have identified the issue and are implementing a fix. Due to a recent change on Google Meet copilot bots are unable to join some of the Google Meet meetings. Team has found a fix and is working on implementing it. The next status update will be after the fix has been applied.
Our engineering teams have resolved the issue and we are monitoring the fix.
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.
Starting at approximately 02:00 on 2026-06-02 UTC Google began rolling out a change that was incompatible with Clari Copilot Google Meet recorder bots. This impacted a subset of customers using Google Meet preventing the bots from joining calls. Clari engineering team identified the change and rolled out a fix at 12:47 2026-06-03 UTC resolving the issue.
The Clari Revenue platform is currently seeing an increase in errors in Inspection and Forecasting modules. Our engineering team is actively investigating the issue.
Our engineering teams have implemented a fix which has addressed the observed errors. We are monitoring the system to confirm the issue has been 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.
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.
CRM syncing is showing a delay of a a few hours. we expect the delay to be caught up by 8:00 AM UTC
Our engineering teams have resolved the issue and we are monitoring the fix.
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.
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.
Groove is currently experiencing intermittent performance issues, and you may notice some slowness. Our engineers are actively investigating and will share updates as soon as possible.
Our engineering teams have resolved the issue and we are monitoring the fix.
This incident has been resolved.
Our engineering team is actively investigating reported issues with the Analytics module.
We have identified and reverted the related change. Behavior is returning to normal and we will continue to monitor system health.
We have confirmed the issue has been resolved for all impacted users. A summary of the incident will be posted.
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.
Our engineering team is actively investigating reports of the Forecasting tab not appearing for some customers.
We have identified the cause of the missing Forecasting tabs and are working to resolve.
We have restored the Forecasting tab and are monitoring to confirm that all users have access.
We have confirmed the issue has been resolved for all impacted users.
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.
Clari Copilot users are currently not receiving any email notifications. Our engineering team is actively investigating the issue. The issue is only limited to the Clari Copilot product.
We are continuing to investigate the issue. Email notifications remain impacted.
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.
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.
We are currently investigating an issue where Clari Copilot is not recording some Zoom calls
Some Clari Copilot calls via Zoom continue to not be recorded. Our engineering team is currently working with Zoom to resolve this issue.
We are continuing to work with the Zoom engineering team to resolve this issue. We will provide additional details about the progress as they become available.
Our engineering teams have resolved the issue together with the Zoom engineering team and we are monitoring the fix.
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.
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.
We’re aware of an issue affecting links in some email content, and our engineering teams are actively working to resolve it as quickly as possible.
We've spotted that something has gone wrong. We're currently working our partners to remediate the issue, and will provide an update soon.
We’re aware of an issue affecting links in some email content,. We're actively working with our partners to remediate the issue, and will provide an update soon.
The issue affecting links in some email content, has been resolved. Thank you for your patience and understanding.
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.
We are investigating an issue where Clari Copilot is not recording calls made via Zoom for some customers.
Our engineering team has put in place a temporary workaround and are working with the external vendor for a long term solution.
The issue continues to impact a subset of our customers despite the workaround. Some users will see a consent prompt before recording begins, which is expected. We are investigating the recent failures and will provide updates as they become available.
The investigation continues and updates will be provided as new information becomes available.
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.
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.
A recent update to eliminate duplicate columns in the opportunity grid has caused the grid columns to become re-ordered for some customers. Our engineering team is actively investigating.
Our engineering teams have identified the issue and are implementing a fix. The change to eliminate duplicate columns had the undesired side-effect of changing the ordering of the remaining columns. The team is working to roll back the change. The next status update will be after the fix has been applied.
We have confirmed the issue has been resolved for all users. A summary of the incident will be posted within the next three US business days.
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.