预测、检查和板板没有达到预期效果
Outage重大事件
受影响的组件
Forecast
- investigating
有些顾客可能发现Dashboard、预测和检查有问题 我们的工程组正在积极调查.
- monitoring
我们的工程小组已经解决了这个问题,我们正在监测修复工作.
- resolved
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
自动翻译自官方事件更新。
60 Clari incidents · 2025年2月 — official updates, affected components, duration and resolution details.
有些顾客可能发现Dashboard、预测和检查有问题 我们的工程组正在积极调查.
我们的工程小组已经解决了这个问题,我们正在监测修复工作.
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
自动翻译自官方事件更新。
我们的工程队意识到这个问题与第三方停工有关,并正在监测这个问题的进展情况。 没有为副驾驶呼叫生成智能摘要。 呼叫处理工作仍在进行,一旦停用问题得到解决,将生成摘要.
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
2026-09-08 UTC下午约18:30-20:30,第三方流线数据提供者的停电中断了生成Copilot智能摘要的管道,防止了呼叫摘要生成. 电话录音和录音继续正常工作。 一旦供应商解决问题,我们的系统自动恢复处理,2026-09-09年完成回填工作,生成所有符合条件的受影响电话摘要.
自动翻译自官方事件更新。
我们发现系统的某些部分在加载页面时会经历较长的反应时间. 我们目前正在调查这一问题,并将很快提供最新情况.
一项措施已经执行,我们正在监测结果.
我们的工程组已经解决这个问题,因此,系统功能已恢复正常
自动翻译自官方事件更新。
我们目前正在调查这一问题.
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
2026-09-02 协调世界时约07:57-09:16之间,部分用户无法在Claria应用程序上签字. 事件由行政变动所引发,这种变动意外地影响了克拉里用户的认证. 我们的团队恢复了正常的认证服务,所有Claria服务目前都正常运行.
自动翻译自官方事件更新。
我们收到客户的报告称,他们的销售力量集成用户因象征性过期而中断。 我们的工程组正在积极调查.
少数客户由于象征性过期而中断了销售力量集成用户。 发生这种情况时,进入Claria的常规数据同步无法运行. 我们的工程队 以及销售部队的支持 正在调查这个问题。 自2026-08-16起没有观察到新的断开. 如果您的集成用户已断开, 您可以重新连接以解决同步问题 。 需要帮助时,请联系支援部寻求帮助.
这个问题似乎是与销售部队的一次性事件。 我们继续监测任何再次发生的情况,并积极争取销售力量的支持,以了解发生的情况以及如何避免再发生。 我们将把这个记录留在"监测"状态中,直到我们对事件有满意的理解,但不会期望进一步更新.
我们从"销售力量"中确认 造成受影响用户停电的原因 事件概要将在未来三个美国工作日内公布.
2026-08-16日,一个销售力量超强迁移导致销售力量和Claria之间的连接中断,跨越了一小组客户账户. 这个问题暂时暂停了对一些组织的自动数据更新,要求其用户重新使用 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.
目前,我们正在调查关于Claria平台间歇性出入问题的报告。 客户可能难以访问应用程序,或遇到缓慢的表现。 我们的工程队正在积极努力解决这一问题。 一旦获得更多信息,我们将提供最新资料.
我们的工程队已经解决这个问题,系统性能正在恢复正常. 我们正在继续监测这项措施.
在对该问题进行了3小时的监测之后,我们没有看到任何再起,而且该平台一直保持稳定。 事件概要将在未来三个美国工作日内公布.
在协调世界时2026-07-27 13:15左右,一些用户在尝试使用Claria应用程序时经历了长的页面载荷时间和出错. 工程组能够确定,我们一些以云为基础的服务在规模化方面存在的问题是问题的根源,并部署了一个固定装置来恢复系统性能. 系统在协调世界时2026-07-27 15:30恢复了正常运行,停用期间没有客户数据面临风险.
自动翻译自官方事件更新。
一些客户在"Zoom"中可能会遇到Claria Copilot通话录音的问题. 我们的工程组正在积极调查.
我们的工程组仍在积极调查 问题在于影响客户依赖网络记录器进行Zoom录音. 一旦获得更多信息,我们将提供另一个最新情况.
受影响的客户继续看到Zoom网上的记录器的问题。 我们的工程小组正在Zoom的支持下积极调查,并审查其他路径,以便受影响客户恢复记录功能。 一旦获得更多信息,我们将提供另一个最新情况.
这个问题仍在调查之中。 受影响的客户在Zoom网站上的网络记录器方面继续遇到问题。 我们的调查显示,最近Zoom的平台行为的变化使得一些记录员无法参加客户会议. 我们的工程组正与Zoom Support公司积极合作解决这一问题。 一旦获得更多信息,我们将提供另一个最新情况.
我们的工程小组已经查明了问题,并正在执行一个解决办法.
我们发布了应用中指南,指示受影响的客户在Claria Copilot中重新连接到他们的Zoom集成,让客户恢复了Copilot记录Zoom会议的能力.
我们与Zoom合作解决了影响网络记录器的问题。 记录现已按预期运作。 我们的工程组正在监测该系统,如果有任何变化,我们将提供另一个最新情况。 对于受到影响的客户,包括以前重新连通其 " 缩放 " 整合的客户,不需要采取进一步行动。 如果你还遇到问题 请联系我们的支援小组.
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
从协调世界时2026-07-13 06:30左右开始,Zoom平台的改变影响了Claria Copilot's Zoom网络记录器加入和记录会议的能力. 因此,一些客户无法在受影响期间记录Zoom会议。 这个问题只影响到Zoom网络记录;其他记录器平台没有受到影响。 这一时期排定的录音会议可能没有记录。 克拉里工程组在发现问题后与Zoom密切合作,调查变化,确定其影响,并采取必要的缓解措施. Zoom web recorders joins已恢复正常运行,我们确认在协调世界时约2026-07-15 11:08完全恢复. 我们正在继续与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.
我们的工程团队正在积极调查所有三个平台的根源。 我们正在密切监控呼叫记录成功率 并将随着我们了解更多情况提供最新消息.
我们确认,已经为受影响的用户解决了这一问题。 事件概要将在未来三个美国工作日内公布.
从协调世界时2026-06-22日08:23开始,一些Claria Copilot客户在Zoom、Google Meet和Microsoft Teams之间遭遇了失败, 出错可追溯到2026-06-20日的"副驾驶"维护以及未完全应用的配置变化. Claria工程组通过应用配置变化并验证变化来补救这个问题. 呼叫录音功能于UTC2026-06-22. 18:40左右恢复. 我们在今后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.