Pipefy incident

(Integrations) Flow executions are experiencing delay on processing time

Notice Resolved

Pipefy experienced a notice incident on May 5, 2026, lasting 4h 28m. The incident has been resolved; the full update timeline is below.

Started
May 05, 2026, 03:06 PM UTC
Resolved
May 05, 2026, 07:35 PM UTC
Duration
4h 28m
Detected by Pingoru
May 05, 2026, 03:06 PM UTC

Update timeline

  1. investigating May 05, 2026, 03:06 PM UTC

    Dear customers, We are currently aware of an issue affecting a subset of our customers where iPaaS flow executions are experiencing longer-than-expected processing times. We want to be transparent: Your flows are running. The behavior some customers are noticing is a delay in the time it takes for each process to be picked up and started — once a run begins, it proceeds normally. Our engineering teams are actively investigating the root cause and working to restore standard processing times as quickly as possible. We do not have an ETA to share at this moment, but we are committed to keeping you informed as the situation evolves. If you have been impacted, no action is required on your end. We will provide updates in our Statuspage as they become available. We apologize for any inconvenience this may cause and appreciate your patience.

  2. resolved May 05, 2026, 08:05 PM UTC

    This incident was resolved after a fix being implemented