Pipefy incident
Custom Integrations | Slowness when executing any action
Affected components
Update timeline
- investigating Feb 25, 2026, 02:32 PM UTC
We are currently investigating this issue.
- monitoring Feb 25, 2026, 02:50 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Feb 25, 2026, 03:31 PM UTC
We are continuing to monitor for any further issues.
- resolved Feb 25, 2026, 03:56 PM UTC
This incident has been resolved.
- postmortem Mar 02, 2026, 09:14 PM UTC
**Root Cause** The issue was caused by exceeding the execution limit in integration queues, leading to a loop in automation that triggered numerous webhooks. This resulted in an overload of a specific flow, creating a large processing queue. Consequently, clients experienced delays in their process executions. **Resolution** To resolve the issue, the customer service account was deactivated, which helped alleviate the problem. **Action Plan** To prevent future occurrences, a rate limit will be activated on the system, and the timeout for execution flows will be reduced.
Looking to track Pipefy downtime and outages?
Pingoru polls Pipefy's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when Pipefy reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track Pipefy alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required