Pipefy incident

Issues affecting AI Features (Analytics, Builder, and Assistant)

Critical Resolved View vendor source →

Pipefy experienced a critical incident on January 28, 2026 affecting AI Assistant, lasting 21m. The incident has been resolved; the full update timeline is below.

Started
Jan 28, 2026, 11:58 AM UTC
Resolved
Jan 28, 2026, 12:19 PM UTC
Duration
21m
Detected by Pingoru
Jan 28, 2026, 11:58 AM UTC

Affected components

AI Assistant

Update timeline

  1. investigating Jan 28, 2026, 11:58 AM UTC

    We are currently investigating an issue that is causing downtime for our AI-powered tools, including AI Analytics, AI Builder, and the AI Assistant. Our engineering team is working to restore service as quickly as possible. We apologize for any inconvenience.

  2. identified Jan 28, 2026, 11:59 AM UTC

    The root cause has been identified and we are currently deploying a resolution to fix the outages in our AI suite. We are monitoring the recovery of AI Analytics, AI Builder, and AI Assistant and expect services to return to normal shortly.

  3. resolved Jan 28, 2026, 12:19 PM UTC

    We have successfully deployed a fix and confirmed that AI Analytics, AI Builder, and AI Assistant are fully operational. We will continue to monitor the performance for a short period to ensure ongoing stability. Thank you for sticking with us!

  4. postmortem Mar 10, 2026, 09:18 PM UTC

    Summary: **The incident involved an outage affecting AI analytics, AI builder, and AI Assistant functionalities. Although the platform itself remained accessible, these specific AI applications experienced disruptions due to a configuration error.** Impact: **The outage impacted the AI-related functionalities within the platform, potentially affecting users who rely on AI analytics, AI builder, and AI Assistant for their operations. While the core platform was not down, the unavailability of these AI features could have hindered users' ability to perform tasks that depend on AI capabilities.** Root Cause: **The root cause of the issue was identified as an incorrect configuration in the SDK package, which led to the malfunction of the AI applications. This misconfiguration necessitated corrective actions to restore functionality.** Corrective Actions: * The issue with the SDK configuration was fixed. - Smoke tests on the SDK pipeline were enhanced to prevent similar issues in the future. - Initiated the process to invalidate the cache on the SDK. - Improvements were made to the rollback process to ensure quicker recovery in case of future incidents. Next Steps/Conclusion: **We will continue to monitor the system closely to ensure stability and prevent future issues. Our ongoing efforts are focused on enhancing the customer experience by ensuring the reliability and performance of our AI functionalities.**