Jitterbit incident

LATAM: Wevo iPaaS is facing slowness during execution logs processing

Minor Resolved View vendor source →

Jitterbit experienced a minor incident on July 17, 2025 affecting Runtime Flow Logs, lasting 2h 24m. The incident has been resolved; the full update timeline is below.

Started
Jul 17, 2025, 11:55 AM UTC
Resolved
Jul 17, 2025, 02:20 PM UTC
Duration
2h 24m
Detected by Pingoru
Jul 17, 2025, 11:55 AM UTC

Affected components

Runtime Flow Logs

Update timeline

  1. investigating Jul 17, 2025, 11:55 AM UTC

    We are currently investigating an issue affecting the performance of Flow Execution log processing on the Wevo iPaaS Platform. As a result, it may appear that flows are not running as expected, even though they are being executed. We appreciate your patience while we work to resolve this issue.

  2. identified Jul 17, 2025, 12:18 PM UTC

    The root cause of the issue has been identified, and our team is actively working on implementing a solution.

  3. monitoring Jul 17, 2025, 01:12 PM UTC

    A fix has been implemented, and we are currently monitoring the results. Due to the earlier slowness in Flow Execution log processing, a backlog of logs has accumulated. All pending messages are expected to be fully processed over the next few hours. Our team will continue to monitor the platform closely until the backlog is cleared and normal processing times are fully restored.

  4. resolved Jul 17, 2025, 02:20 PM UTC

    This incident has been resolved. The backlog of Flow Execution logs has been fully processed, and the system has returned to normal processing times.