57 Clari incidents · febbraio 2025 — official updates, affected components, duration and resolution details.
Stiamo attualmente indagando su questo problema.
Abbiamo confermato che il problema è stato risolto per gli utenti colpiti. Un riassunto dell'incidente sarà pubblicato entro i prossimi tre giorni lavorativi americani.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Abbiamo ricevuto segnalazioni da parte dei clienti che il loro utente di integrazione Salesforce è stato disconnesso a causa della scadenza di token. Il nostro team di ingegneri sta indagando attivamente.
Un piccolo numero di clienti ha avuto il loro utente di integrazione Salesforce scollegato a causa della scadenza token. Quando questo accade, i dati regolari sincronizzati in Clari non è in grado di eseguire. Il nostro team di ingegneri insieme al supporto di Salesforce sta indagando sul problema. Nessuna nuova disconnessione è stata osservata dal 2026-08-16. Se l'utente di integrazione è stato disconnesso, è possibile riconnetterlo per risolvere il problema di sincronizzazione. Se avete bisogno di aiuto, si prega di contattare il supporto per ottenere assistenza.
Il problema sembra essere stato un evento di una volta con Salesforce. Continuiamo a monitorare per qualsiasi ricorrenza e siamo attivamente impegnati con il supporto di Salesforce per capire cosa è successo e come evitare ulteriori eventi. Lasceremo questo record in "monitoraggio" stato fino a quando non abbiamo una comprensione soddisfacente circa l'incidente, ma non si aspettano di fare ulteriori aggiornamenti.
Abbiamo confermato da Salesforce ciò che ha causato il outage per gli utenti colpiti. Un riassunto dell'incidente sarà pubblicato entro i prossimi tre giorni lavorativi americani.
Il 2026-08-16, una migrazione di Salesforce Hyperforce ha causato interruzioni di connessione tra Salesforce e Clari attraverso un piccolo gruppo di clienti. Questo numero ha temporaneamente sospeso aggiornamenti automatizzati di dati per alcune organizzazioni e ha richiesto ai loro utenti di riauthenticate con Salesforce. Non c'è modo noto per evitare questa situazione per future migrazioni Hyperforce, ma continuiamo a lavorare con Salesforce per esplorare le opzioni.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading . The next status update will be after the fix has been applied.
Our engineering teams have identified the issue and are implementing a fix. Some or all the pages are not loading The next status update will be after the fix has been applied.
The underlying problem has been fixed, we are monitoring to ensure full functionality is restored.
We are continuing to monitor for any further issues.
We have confirmed the issue has been resolved for the impacted users. No new errors have been observed in last 60 minutes of monitoring. All the impacted components are fully operational now. A summary of the incident will be posted within the next three US business days.
At approximately 2026-08-05 00:02 UTC, a subset of organizations experienced errors when attempting to access the Clari application. Affected users saw the message: "Something went wrong with loading application resources." Our engineering team identified a regression introduced in a recent deployment and issued a hotfix. Systems returned to normal operations at 2026-08-05 13:30 UTC . No customer data was at risk at any point during this incident.
Stiamo attualmente indagando i rapporti di problemi di accesso intermittente con la piattaforma Clari. I clienti possono sperimentare difficoltà ad accedere all'applicazione o incontrare prestazioni lente. Il nostro team di ingegneri sta lavorando attivamente per risolvere questo problema. Forniremo aggiornamenti come ulteriori informazioni diventano disponibili.
I nostri team di ingegneria hanno risolto il problema e le prestazioni del sistema stanno tornando alla normalità. Stiamo continuando a monitorare la correzione.
Dopo aver monitorato il problema per 3 ore, non abbiamo visto alcuna riostanze e la piattaforma è stata stabile. Un riassunto dell'incidente sarà pubblicato entro i prossimi tre giorni lavorativi americani.
A circa 2026-07-27 13:15 UTC alcuni utenti hanno sperimentato i tempi di carico e gli errori di lunga data durante il tentativo di utilizzare l'applicazione Clari. Il team di ingegneria è stato in grado di determinare che un problema con la scala di alcuni dei nostri servizi cloud-based è stata la fonte del problema e ha implementato una correzione per ripristinare le prestazioni del sistema. Sistemi restituiti alle normali operazioni a partire dal 2026-07-27 15:30 UTC e nessun dato del cliente era a rischio durante l'interruzione.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
Alcuni clienti potrebbero avere problemi con le registrazioni delle chiamate Clari Copilot in Zoom. Il nostro team di ingegneri sta indagando attivamente.
Il nostro team di ingegneri sta ancora indagando attivamente. Il problema sta influenzando i clienti che si affidano ai registratori web-based per le registrazioni Zoom. Forniremo un altro aggiornamento non appena saranno disponibili ulteriori informazioni.
I clienti colpiti continuano a vedere i problemi con i registratori web su Zoom. Il nostro team di ingegneria sta attivamente indagando con il supporto Zoom e la revisione di percorsi alternativi per i clienti colpiti per riprendere la funzionalità di registrazione. Forniremo un altro aggiornamento non appena saranno disponibili ulteriori informazioni.
Il problema e' ancora sotto indagine. I clienti affetti continuano a sperimentare problemi con i registratori web su Zoom. La nostra indagine indica che i recenti cambiamenti nel comportamento della piattaforma di Zoom impediscono ad alcuni registratori di unirsi alle riunioni dei clienti. Il nostro team di ingegneri sta lavorando attivamente con Zoom Support per risolvere il problema. Forniremo un altro aggiornamento non appena ulteriori informazioni saranno disponibili.
I nostri team di ingegneria hanno identificato il problema e stanno implementando una soluzione.
Abbiamo pubblicato una guida in-app che indirizza i clienti interessati a riconnettere la loro integrazione Zoom in Clari Copilot, consentendo ai clienti di ripristinare la capacità di Copilot di registrare incontri Zoom.
Abbiamo lavorato con Zoom per risolvere il problema che riguarda i registratori web-based. Le registrazioni funzionano come previsto. Il nostro team di ingegneria sta monitorando il sistema, e forniremo un altro aggiornamento se qualcosa cambia. Per i clienti colpiti, compresi quelli che hanno precedentemente riconnesso la loro integrazione Zoom, non è necessaria alcuna ulteriore azione. Se stai ancora vivendo problemi, contatta il nostro team di supporto.
Abbiamo confermato che il problema è stato risolto per gli utenti colpiti. Un riassunto dell'incidente sarà pubblicato entro i prossimi tre giorni lavorativi americani.
A partire dal 2026-07-13 06:30 UTC, un cambiamento nella piattaforma di Zoom ha influenzato la capacità del web recorder di Clari Copilot di unirsi e registrare gli incontri. Di conseguenza, alcuni clienti non sono stati in grado di registrare incontri Zoom in Copilot durante il periodo di impatto. Questo problema ha influenzato solo la registrazione web di Zoom; altre piattaforme di registrazione non sono state interessate. Le riunioni programmate per la registrazione durante questo periodo potrebbero non essere state registrate. Dopo aver individuato il problema, il team di ingegneria Clari ha lavorato a stretto contatto con Zoom per indagare il cambiamento, determinare il suo impatto e implementare le necessarie mitigazioni. Zoom web recorder unioni sono tornati al normale funzionamento, e abbiamo confermato il recupero completo di circa 2026-07-15 11:08 UTC. Stiamo continuando a lavorare con Zoom per comprendere meglio il cambiamento e per rafforzare la nostra integrazione in modo che i cambiamenti simili della piattaforma possano essere gestiti con più grazia in futuro.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.
Il nostro team di ingegneri sta attivamente indagando sulla causa principale su tutte e tre le piattaforme. Stiamo monitorando i tassi di successo di registrazione delle chiamate da vicino e fornirà aggiornamenti mentre impariamo di più.
Abbiamo confermato che il problema è stato risolto per gli utenti colpiti. Un riassunto dell'incidente sarà pubblicato entro i prossimi tre giorni lavorativi americani.
A partire dalle 08:23 UTC il 2026-06-22 alcuni clienti di Clari Copilot hanno sperimentato guasti attraverso Zoom, Google Meet e Microsoft Team che hanno impedito di registrare le chiamate. Gli errori sono stati ricondotti alla manutenzione Copilota il 2026-06-20 e le modifiche di configurazione non completamente applicate. Il team Clari Engineering ha risolto il problema applicando le modifiche di configurazione e convalidando le modifiche. La funzionalità di registrazione delle chiamate è stata ripristinata a circa 18:40 UTC 2026-06-22. Abbiamo continuato a monitorare il sistema per le prossime 24 ore per garantire che non ci fossero ulteriori problemi prima di risolvere l'incidente.
Tradotto automaticamente dall'aggiornamento ufficiale dell'incidente.
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.