Pendo: Error thrown in continuing Leo conversations
Affected components: JPN environment (app.jpn.pendo.io) - Pendo UIPendo UIPendo UIUS environment (app.pendo.io) - Pendo UIPendo UIUS1 environment (us1.app.pendo.io) - Pendo UIEU environment (app.eu.pendo.io) - Pendo UIPendo UI
Timeline of updates
- identified
We are investigating a disruption affecting Pendo's AI assistant, Leo. Some customers may be unable to continue a conversation with Leo after the first message. Our team has identified the behavior and is deploying a fix. Further updates will follow.
- monitoring
We have tested and deployed a fix and the issue with continuing conversations in Leo should be resolved. We will continue to monitor the fix for a period of time before resolving the issue.
- resolved
This incident is resolved.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3025f4daee72d0fa…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Pendo, started 2026-07-27 14:48 UTC, resolved after 37 min, 3 update(s).
- Title
- Error thrown in continuing Leo conversations
- Vendor
- Pendo
- Date
- URL
- https://rewindex.com/company/pendo/incidents/3slx669g0kxq
Pendo profileRecent Pendo incidentsAll outages on July 27, 2026Pendo in July 2026MarkdownJSON