Pipefy incident

Failure on personal acess token

Minor Resolved View vendor source →

Pipefy experienced a minor incident on December 18, 2025, lasting 32m. The incident has been resolved; the full update timeline is below.

Started
Dec 18, 2025, 03:00 PM UTC
Resolved
Dec 18, 2025, 03:33 PM UTC
Duration
32m
Detected by Pingoru
Dec 18, 2025, 03:00 PM UTC

Update timeline

  1. investigating Dec 18, 2025, 03:00 PM UTC

    We identified that some personal acess token are experience some issue, we already working on this fix

  2. investigating Dec 18, 2025, 03:29 PM UTC

    The team is working on script to running to the personal accounts that did not log in for the past 90 days

  3. resolved Dec 18, 2025, 03:33 PM UTC

    This incident has been resolved.

  4. postmortem Dec 18, 2025, 08:32 PM UTC

    **Root Cause** A critical incident occurred due to a strategic update aimed at resolving security issues related to email feature. This incident affected key processes, including Integrations and AI automations, leading to failures in customer workflows. **Resolution** To resolve the issue, the team had to reverse the changes and execute a script to restore user accounts. This action was necessary to ensure the stability and functionality of the affected users. **Action Plan** * Future actions include setting up alerts for agent requests and specific error codes * Understanding the limitations of current alerts to be more proactive on this scenarios * Improve tests scenarios for cacth error previously