Pipefy incident

Custom Integrations | Slowness when executing any action

Major Resolved View vendor source →

Pipefy experienced a major incident on February 25, 2026 affecting Integrations, lasting 1h 23m. The incident has been resolved; the full update timeline is below.

Started
Feb 25, 2026, 02:32 PM UTC
Resolved
Feb 25, 2026, 03:56 PM UTC
Duration
1h 23m
Detected by Pingoru
Feb 25, 2026, 02:32 PM UTC

Affected components

Integrations

Update timeline

  1. investigating Feb 25, 2026, 02:32 PM UTC

    We are currently investigating this issue.

  2. monitoring Feb 25, 2026, 02:50 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. monitoring Feb 25, 2026, 03:31 PM UTC

    We are continuing to monitor for any further issues.

  4. resolved Feb 25, 2026, 03:56 PM UTC

    This incident has been resolved.

  5. 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.