Pipefy incident

Application Instability

Notice Resolved

Pipefy experienced a notice incident on April 23, 2026, lasting —. The incident has been resolved; the full update timeline is below.

Started
Apr 23, 2026, 06:48 PM UTC
Resolved
Apr 04, 2018, 02:14 PM UTC
Duration
—
Detected by Pingoru
Apr 23, 2026, 06:48 PM UTC

Update timeline

  1. resolved Apr 23, 2026, 06:48 PM UTC

    We identify the problem, it happened because the gem [sequenced](https://github.com/derrickreimer/sequenced) that we use in our Ruby project locked the phase table, after that this process died and table stay locked. We kill the process and restart the application that returns to respond as expected. Now we are removing that gem and move this logic to our database that can do this job in the same process and prevent this error.

  2. resolved Apr 23, 2026, 06:48 PM UTC

    All systems are operational now. We will keep monitoring our Application and Databases. More information will be provided as soon as possible.

  3. investigating Apr 23, 2026, 06:48 PM UTC

    Our team are investigating a high error and timeout rate which is causing instability in our service. More details will be provided soon.