Pipefy incident

Automations Slowness

Minor Resolved View vendor source →

Pipefy experienced a minor incident on September 25, 2025 affecting Automation, lasting 2h 8m. The incident has been resolved; the full update timeline is below.

Started
Sep 25, 2025, 02:22 PM UTC
Resolved
Sep 25, 2025, 04:31 PM UTC
Duration
2h 8m
Detected by Pingoru
Sep 25, 2025, 02:22 PM UTC

Affected components

Automation

Update timeline

  1. investigating Sep 25, 2025, 02:22 PM UTC

    We are currently investigating this issue.

  2. identified Sep 25, 2025, 02:49 PM UTC

    The issue has been identified and a fix is being implemented.

  3. monitoring Sep 25, 2025, 03:02 PM UTC

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

  4. resolved Sep 25, 2025, 04:31 PM UTC

    This incident has been resolved.

  5. postmortem Oct 02, 2025, 08:28 PM UTC

    **Root Cause** The system experienced slowness due to multiple updates being processed simultaneously, which led to delays and a backlog of tasks. This was caused by bulk actions affecting the same field. **Resolution** To prevent further issues, we isolated the affected processes into a dedicated queue, ensuring that any high volume or problems would not impact other users. Additionally, we adjusted the number of workers to manage the load effectively. **Action Plan** We moved the affected processes to a specialized queue and reduced the number of workers to handle tasks more efficiently. We also reviewed logs to identify the cause of the backlog and are considering setting limits and prioritization queues. Further actions include enhancing logging for better issue identification and potentially redesigning the process for improved performance.