Pipefy incident

Indexing Delay

Minor Resolved

Pipefy experienced a minor 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
May 30, 2018, 06:49 PM UTC
Duration
—
Detected by Pingoru
Apr 23, 2026, 06:48 PM UTC

Update timeline

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

    The cause of indexing delay was a high CPU usage in the cluster. We had to stop the processing of our Elasticsearch jobs in order to restore the cluster heatlh. The cluster is backing to normal status and we are gradually restarting our Elasticsearch queues. The root cause of this CPU spike is being investigated with our cloud provider.

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

    We are currently investigating a indexing delay in our Elasticsearch cluster.

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

    Almost all our background queues and indexing jobs finished. We are still working on a few indexing jobs and still monitoring the workers and Elasticsearch cluster.

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

    This incident has been resolved. All our queues and Elasticsearch cluster are up and running normally. We will keep investigating the root cause and will work in order to improve our infrastructure.