60 Clari incidents · 2025年2月 — official updates, affected components, duration and resolution details.
一部の顧客は、ダッシュボード、予測、検査の問題を見ることができます 当社のエンジニアリングチームは積極的に調査しています.
当社のエンジニアリングチームは、問題を解決し、修正を監視しています.
影響を受けたユーザーに対して、問題が解決されたことを確認しました。 次の3営業日以内に事件の要約を掲示します.
公式のインシデント更新を自動翻訳しています。
当社のエンジニアリングチームは、第三者の停電に関連するこの問題を認識し、その問題の進捗状況を監視しています。 Copilotの呼び出しでスマートの要約は生成されません。 呼び出し処理は、停電が解決されると、呼び出し処理が機能し、集計が生成されます.
影響を受けたユーザーに対して、問題が解決されたことを確認しました。 次の3営業日以内に事件の要約を掲示します.
2026-09-08 は、サードパーティのストリーミングデータプロバイダで、Copilotのスマートな要約を生成するパイプラインを中断し、コールサマリーの発生を防ぎました。 通話録音と転写は正常に動作し続けます。 プロバイダーが問題を解決したら、2026-09-09-09-09 で完了したシステムは自動的に処理を再開し、影響を受けるすべてのコールの合計を生成する.
公式のインシデント更新を自動翻訳しています。
ページの読み込み時に、システムの一部が長い応答時間を経験していることを確認しました。 現在、課題を調査し、早期にアップデートを行います.
修正を実装し、結果を監視しています.
当社のエンジニアリングチームは、問題が解決され、その結果、システム機能が正常に復元されています
公式のインシデント更新を自動翻訳しています。
現在、この問題を調査中です.
影響を受けたユーザーに対して、問題が解決されたことを確認しました。 次の3営業日以内に事件の要約を掲示します.
2026-09-02 で 約 07:57-09:16 UTC, 一部のユーザーはClari アプリケーションにサインインできませんでした. 事故は、Clariユーザーの予期しない認証に影響を及ぼした管理変更によってトリガーされました。 当社のチームは、通常の認証サービスを復元し、すべてのクラリサービスが正常に動作しています.
公式のインシデント更新を自動翻訳しています。
弊社では、Salesforce のインテグレーション ユーザがトークンの有効期限のために接続されていないという顧客からのレポートを受け取りました。 当社のエンジニアリングチームは積極的に調査しています.
少数のお客様が、Salesforce のインテグレーション ユーザがトークンの有効期限のために接続解除を解除しました。 この場合、通常のデータをClariに同期させると実行できません。 Salesforceサポートと連携したエンジニアリングチームが課題を調査しています。 2026-08-16以降、新しい切断が見られません。 統合ユーザが接続されていない場合、同期問題を解決するために再接続できます。 助けが必要な場合は、サポートまでご連絡下さい.
問題は Salesforce で 1 回限りのイベントだったようです。 今後も、あらゆる再発を監視し、セールスフォースのサポートに積極的に取り組んでまいります。 この記録は、事件についての満足な理解を持っているまで「監視」状態に残しますが、さらなる更新を期待しないでください.
弊社では、影響を受けたユーザーに対しての停電を引き起こしたSalesforceから確認しています。 次の3営業日以内に事件の要約を掲示します.
2026-08-16 では、Salesforce と Clari 間での Salesforce Hyperforce のマイグレーションによる接続の中断が顧客アカウントの小さなグループ全体で発生しました。 この問題は、一部の組織に自動データ更新を一時的に使用し、ユーザーがSalesforceで再認証する必要があります。 将来のHyperforceマイグレーションのこの状況を回避する方法は知られていませんが、引き続きSalesforceと連携してオプションを探ります.
公式のインシデント更新を自動翻訳しています。
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.
現在、Clariプラットフォームで断続的なアクセス問題のレポートを調査しています。 お客様が、アプリケーションへのアクセスが困難であるか、または遅いパフォーマンスに遭遇する可能性があります。 当社のエンジニアリングチームは、この問題を解決するために積極的に取り組んでいます。 最新情報をお届けいたします.
当社のエンジニアリングチームは、問題とシステムのパフォーマンスが正常に戻ります。 修正を監視し続けています.
3時間の問題を監視した後、再発が見つからず、プラットフォームは安定しています。 次の3営業日以内に事件の要約を掲示します.
約2026-07-27 13:15 UTC一部のユーザーは、Clariアプリケーションを使用した場合、長いページの読み込み時間とエラーが発生しました。 エンジニアリングチームは、クラウドベースのサービスの一部をスケーリングする問題が問題のソースであり、システムのパフォーマンスを復元するための修正をデプロイしたことを決定できるようになりました。 システムは、2026-07-27 15:30 UTC で正常な操作に戻っておらず、停電時に顧客データが危険にならなかった.
公式のインシデント更新を自動翻訳しています。
一部の顧客は、ZoomのClari Copilotコール録画で問題が発生することがあります。 当社のエンジニアリングチームは積極的に調査しています.
当社のエンジニアリングチームは、まだ積極的に調査しています。 問題は、ズーム記録のためのWebベースのレコーダーに依存する顧客に影響を与える. 情報が増え次第、更新を行います.
影響を受けたお客様は、Zoom の Web ベースのレコーダーの問題を引き続き確認しています。 当社のエンジニアリングチームは、Zoomサポートに積極的に投資し、影響を受けた顧客に代わりのパスを見直し、録画機能を再開します。 情報が増え次第、更新を行います.
問題はまだ調査中です。 顧客がZoomでWebベースのレコーダーで問題を経験し続ける影響を受けました。 当社の調査では、Zoomのプラットフォーム行動の最近の変化は、顧客会議への参加から一部のレコーダーを防ぐことを示しています。 当社のエンジニアリングチームは、問題の解決にZoomサポートを積極的に取り組んでいます。 情報が増え次第、更新を行います.
当社のエンジニアリングチームは、問題を特定し、修正を実施しています.
当社は、影響を受けた顧客を直接して、Clari CopilotのZoom統合を再接続し、顧客がCopilotのZoom会議を記録する能力を回復できるようにしました.
Webベースのレコーダーに影響を及ぼす問題を解決するためにZoomと連携しました。 録画は期待通り機能しています。 当社のエンジニアリングチームはシステムを監視し、変更があった場合は別のアップデートを提供します。 影響を受けたお客様は、以前にZoomの統合を再接続した人を含め、さらなるアクションは必要ありません。 問題が発生した場合は、サポートチームにお問い合わせください.
影響を受けたユーザーに対して、問題が解決されたことを確認しました。 次の3営業日以内に事件の要約を掲示します.
約2026-07-13 06:30 UTCでZoomのプラットフォームの変更は、Clari CopilotのZoom Webレコーダーの参加と記録会議の能力に影響しました。 その結果、影響を受けた期間のコピロットでのズーム会議を記録できなかったお客様はいます。 この問題は、ZoomのWebベースの録画のみに影響しました。他のレコーダープラットフォームは影響を受けませんでした。 録画予定の会議は記録されていない場合があります。 Clariエンジニアリングチームは、変更を調査し、その影響を決定し、必要な緩和を実施するためにZoomと密接に連携しました。 ズームウェブレコーダーは通常の動作に戻り、約2026-07-15 11:08 UTCでフルリカバリを確認しました。 私たちは、Zoomと協力して、変更をよりよく理解し、同様のプラットフォームの変更が将来的により優雅に処理できるように、統合を強化しています.
公式のインシデント更新を自動翻訳しています。
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.
当社のエンジニアリングチームは、3つのプラットフォーム間で根本的な原因を積極的に調査しています。 コール録音の成功率を密接に監視し、詳細を学ぶためアップデートを提供します.
影響を受けたユーザーに対して、問題が解決されたことを確認しました。 次の3営業日以内に事件の要約を掲示します.
2026-06-22 で 08:23 UTC を始めて、Clari Copilot の顧客は、Zoom、Google Meet、Microsoft Teams を渡る失敗を経験しました。 2026-06-20のCopilotメンテナンスにエラーが追跡され、完全に適用されていない設定変更。 クラリエンジニアリングチームは、構成変更を適用し、変更の有効化することにより、問題の修正を行いました。 通話録音機能は、約18:40 UTC 2026-06-22で復元されました。 今後24時間体制の監視を続け、事故を解決する前に更なる問題がなかったことを確実にします.
公式のインシデント更新を自動翻訳しています。
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.
