Resolved after 9 minutes, affecting AI Assistant, on October 13, 2025.
**Root Cause** The issue arose because the chat records were not linked to the channel object as expected. This lack of connection led to the problems experienced. **Resolution** To resolve the issue, the project was rolled back to a previous version, and changes were reversed. A fix was then applied to ensure that the chat and channel relationship is established, preventing further errors. **Action Plan** During the incident, changes were reversed. Afterward, a fix was implemented to establish the chat-channel relationship, preventing recurrence. Additionally, alerts were set up to notify about any future issues.
Affected components
Update timeline
- investigating Oct 13, 2025, 01:48 PM UTC
We are currently investigating this issue.
- identified Oct 13, 2025, 01:56 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring Oct 13, 2025, 01:56 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Oct 13, 2025, 01:57 PM UTC
We are continuing to monitor for any further issues.
- resolved Oct 13, 2025, 01:57 PM UTC
This incident has been resolved.
- postmortem Oct 28, 2025, 06:13 PM UTC
**Root Cause** The issue arose because the chat records were not linked to the channel object as expected. This lack of connection led to the problems experienced. **Resolution** To resolve the issue, the project was rolled back to a previous version, and changes were reversed. A fix was then applied to ensure that the chat and channel relationship is established, preventing further errors. **Action Plan** During the incident, changes were reversed. Afterward, a fix was implemented to establish the chat-channel relationship, preventing recurrence. Additionally, alerts were set up to notify about any future issues.
Your product runs on more than Pipefy
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services