一些客户无法连接到 Pendo MCP
Issues轻微事件
受影响的组件
MCPMCP
- investigating
一些客户在连接到Pendo MCP时会遇到认证错误,这阻碍了连接的建立. 我们的小组正在积极调查,以确定造成这种破坏的原因。 现有的MCP连接将继续工作到会话到期.
- investigating
我们正在继续调查这种破坏的原因.
- resolved
这一事件已经得到解决.
自动翻译自官方事件更新。
60 Pendo incidents · 2023年4月 — official updates, affected components, duration and resolution details.
一些客户在连接到Pendo MCP时会遇到认证错误,这阻碍了连接的建立. 我们的小组正在积极调查,以确定造成这种破坏的原因。 现有的MCP连接将继续工作到会话到期.
我们正在继续调查这种破坏的原因.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查一个问题 移动设备与Pendo设计器配对失败。 这影响了在多个区域进行设备上引导测试和移动调试. 一旦掌握更多信息,我们将共享最新消息.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们已查明造成干扰的原因, 影响指南针对美国环境的一部分游客, 我们的小组正在积极部署一个固定装置,并将在确认后提供进一步的最新资料.
指南目标已经恢复。 我们正在继续监测任何其他问题.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们为影响登录的中断、引导交货延迟(网络和移动)以及美国环境中的事件数据处理延迟提供了补救。 我们的团队正在积极监测,以确认行为已经完全解决,并将在确认后提供进一步的更新.
我们正在继续监测任何其他问题.
指南可交付性、数据处理和登录已经恢复。 数据没有丢失。 事件处理可能稍有延误.
这一事件已经得到解决.
自动翻译自官方事件更新。
我们正在调查关于用户出乎意料地从Pendo上签字的报告,并促使用户重新登录。 这正在影响美国环境中的一组用户,我们正在调查其他类似行为的其他环境。 我们的团队正在积极努力确定原因。 如果您正在经历此情况, 为 Pendo 域清理您的浏览器缓存和 cookie( 或重新启动您的浏览器) 解决了某些用户的中断 。 我们会分享最新消息,因为我们学到更多.
我们已经调查了这个问题,认为这一事件已经解决.
自动翻译自官方事件更新。
我们正在调查影响潘多的AI助手Leo的干扰事件. 一些客户可能无法在第一次留言后与利奥继续交谈. 我们的团队已经查明了行为 并正在部署一个固定。 随后将进一步提供最新情况.
我们已经测试并部署了一个固定方案,在利奥不断交谈的问题应该得到解决。 在解决这个问题之前,我们将继续监测一段时间.
此事已决.
自动翻译自官方事件更新。
我们正在调查一个中断 影响 潘多如何引导 客户使用 β 版本的 潘多 Web SDK 显示。 稳定的Web SDK上的客户不受影响. 我们的小组正在积极调查,随后将进一步通报最新情况.
我们已经在"Pendo Web SDK"的β版本上确定了影响Pendo指南的行为,其中指南可能会阻止与基础页面的互动. 我们正在部署一个改变 恢复正常的行为。 稳定的Web SDK上的客户不受影响. 随后将进一步提供最新情况.
我们部署了一个改变 以恢复正常的引导行为 在β版本的 Pendo Web SDK。 稳定的Web SDK上的客户不受影响. 我们正在进行监测,以确认全面恢复情况,并将在决议确定后采取后续行动.
这种干扰已经完全解决。 Stable Web SDK在任何时刻都没有受到影响。 谢谢你的耐心.
自动翻译自官方事件更新。
今天上午,在处理即将到来的事件方面出现了拖延。 虽然在此期间没有丢失任何事件,但延误可能会影响以网页和特色观点为依据的指南的针对性。 此时,我们恢复了90%的客户的正常加工期,并应该很快赶上其余客户.
除会话回放活动以外的所有活动都恢复到正常的处理延迟. 我们正在继续就本届会议的积压问题取得进展.
我们正在继续监测任何其他问题.
所有事件处理的延迟都被赶上。 此事已决.
自动翻译自官方事件更新。
我们发现了影响多个数据同步目的地的中断。 已配置数据同步目的地的客户可能会遇到发送失败,并可能收到由Pendo发送的自动目的地故障通知邮件。 我们的工程组正积极努力恢复受灾目的地之间的连通性。 如果您收到目的地失败通知电子邮件, 您此时无需采取任何行动 。 如果需要你们采取步骤,我们将提供最新的指导.
我们恢复了所有受影响的数据同步目的地的连接。 不需要你采取进一步行动。 经常性出口被排队和加工. 某些分娩延误可能持续到周末,但不会导致目的地自动被禁用。 计划于下星期上旬将中断窗口中的任何缺失数据回填,以避免对正在进行的处理和交付造成任何影响。 填满后,我们会发布另一个更新.
这一事件已经得到解决.
自动翻译自官方事件更新。
Between June 3, 2026 and June 4, 2026, some customers experienced two related issues affecting in-app guides on the Pendo platform (pendo.io environment): Guide Targeting Disruption: Guides that used negated, nested segment rules ("Segment is not equal to...") were incorrectly evaluated due to a segment flag processing bug. Affected guides may have failed to display to intended audiences during this window. Conversational AI Guide Editor Unavailable: The Conversational AI interface within the guide editor ("Edit in Pendo") was inaccessible.
Pendo Academy is showing "unauthorized" in all environments. This is not related to user credentials. Our teams are currently investigating the root cause.
This incident has been resolved and Pendo Academy should be accessible across all regions now.
We are currently experiencing a delay in Agent Analytics data processing for customers in our EU region. This is caused by 429 rate limit errors from a third-party AI provider. We will provide an update and resolution as soon as possible.
We have a fix in place that has begun mitigating the issue; we expect full resolution but will continue to monitor for the time being.
This issue is now formally resolved.
We are aware that the issue we believed we had fully resolved yesterday has continued after we employed yesterday's fix. The issue may be impacting some customers' Salesforce integrations. Affected users may experience authentication errors or disruptions to Salesforce-connected features (e.g. our Gong integration for Listen). Our engineering team is actively investigating and working toward a resolution. We will provide further updates as more information becomes available.
We have identified the root cause of the issue and are currently testing the fix before rolling it out to production.
We deployed the fix and will continue to monitor to ensure it resolves the initial issue.
This incident has been resolved.
We are aware of an issue that may be impacting some customers' Salesforce integrations. Affected users may experience authentication errors or disruptions to Salesforce-connected features (e.g. our Gong integration for Listen). Our engineering team is actively investigating and working toward a resolution. We will provide further updates as more information becomes available.
We are working currently to roll out a hotfix to mitigate this issue.
We have deployed a hotfix for the issue impacting Salesforce integrations and are actively monitoring. If your integration is still not syncing, a Pendo admin and a Salesforce user with the proper Salesforce permissions may need to re-authenticate your Salesforce connection manually. To manually reset please 1) Navigate to Subscription Settings > Metadata 2) Scroll to Salesforce Integration 3) Click Begin 4) Authenticate with Salesforce (then following instructions in Salesforce) 5) Finally hit Sync to resume. For more details on Salesforce requirements and set-up, please review the "Prerequisites" and "Set up the connection" sections in the article here: https://support.pendo.io/hc/en-us/articles/16584371535771-Set-up-the-Salesforce-integration-for-Pendo If you continue to experience issues after re-authenticating, please reach out to our support team.
This incident has been resolved.
We are currently investigating an issue affecting guide delivery in the US1 region. Guides are not loading for end users in this environment. Our team is actively working on a resolution.
We have implemented some changes to mitigate the issue with partial restoration, but are still working to fully resolve and identify the root cause of the issue.
Guide delivery in the US1 region has been restore and guides are now loading normally. We are continuing to monitor the situation.
This incident has now been fully resolved.
We are currently experiencing an issue causing Listen email notifications to be unavailable. Our team has identified an issue and has temporarily disabled Listen emails while we work on a fix. All other Pendo email services are unaffected.
We are continuing to work towards a resolution. We will continue to provide updates as they become available.
We are continuing to work on a fix for this issue.
This incident has been resolved.
We are aware of an issue affecting the Visual Design Studio (VDS) where opening a guide for editing may intermittently load a previously opened guide instead of the selected one. In some cases, the guide picker may also appear unexpectedly. Workaround: In the Designer, click the guide name displayed in the top banner to open the guide picker, select the correct guide from the list, and click Proceed to load it. Our engineering team is investigating. We will provide further updates as our investigation progresses. We apologize for any disruption to your workflow.
We are continuing to investigate this issue.
We are continuing to investigate the issue affecting the Visual Design Studio (VDS) where opening a guide for editing may intermittently load a previously opened guide instead of the selected one. In some cases, the guide picker may also appear unexpectedly. Workaround: In the Designer, click the guide name displayed in the top banner to open the guide picker, select the correct guide from the list, and click Proceed to load it. Our engineering team remains actively engaged in the investigation. We will provide additional updates as more information becomes available. We apologize for the continued disruption and appreciate your patience.
We have identified a bug in a code release and are currently working to revert to mitigate this issue using our Visual Designer.
We have successfully reverted the code causing the issue and are monitoring the issue.
We consider this issue fully resolved.
We are aware of an issue affecting users attempting to connect to the Pendo MCP server, where authentication is failing with an "invalid scope" error. Our engineering team has identified the root cause and a fix is currently in progress — we will provide an update once it has been deployed to production.
Our team has identified the issue with a code change on Monday, April 4, which we are currently rolling back.
We have successfully rolled back and are now monitoring the issue.
The rollback we have implemented has successfully fixed the "invalid scope" authentication error and this issue is now resolved.
We are currently investigating an issue where event processing is delayed for a subset of customers. Affected users may notice delays or gaps in analytics data as we work with our vendor to restore full service. We have escalated the issue and are actively monitoring the situation. We will provide updates as more information becomes available.
The root issue causing the event processing day has been identified and we are working with our vendor toward full resolution.
The issue causing delays in event processing has been fully resolved.
This incident has been resolved.
We are currently investigating an issue in our US region where users are unable to edit existing segments. Any attempt to add a rule to a pre-existing segment will result in an error. We are investigating if there are similar impacts to other regions currently. As a workaround, cloning and existing segment or creating new segments works as expected. Our team is working to identify the cause of this issue and we will share an update as soon as possible. We apologize for any inconvenience this may cause.
We have identified the cause of an issue in our US region where users are unable to edit existing segments. Any attempt to add a rule to a pre-existing segment will result in an error. Impact has been narrowed to US region only. We are currently working to roll out a fix. As a workaround, cloning and existing segment or creating new segments works as expected.
We are happy to report that the issue preventing users in our US region from editing existing segments has been fully resolved. All systems are now operating normally, and you can once again edit and manage all of your segments without error. We apologize for the disruption this may have caused and appreciate your patience as we worked to implement a fix.