Integrations slowness

Update timeline

1. investigating Mar 06, 2026, 03:44 PM UTC

   We are currently investigating this issue.

2. investigating Mar 06, 2026, 03:45 PM UTC

   We are continuing to investigate this issue.

3. monitoring Mar 06, 2026, 04:12 PM UTC

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

4. resolved Mar 06, 2026, 05:28 PM UTC

   This incident has been resolved.

5. postmortem Mar 10, 2026, 09:02 PM UTC

   **Root Cause** The issue was caused by a failure in the integration feature, which led to an overload in the system. An unoptimized job created thousands of subflows, quickly filling up memory and affecting system availability. The misuse of the integration was identified as the root cause, prompting the disabling of the problematic flow as an initial step to mitigate the issue. **Resolution** To resolve the issue, the team deactivated the problematic flow and partially cleared the queues. This initial solution aimed to prevent new calls and address the items stuck in the queue. **Action Plan** **We will continue to monitor the system closely to ensure stability and prevent future issues. Our focus remains on continuously improving the customer experience by optimizing our processes and enhancing communication between teams.**