Jitterbit experienced a minor incident on February 3, 2025 affecting Runtime Flow Logs, lasting 1d 10h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Feb 03, 2025, 10:22 AM UTC
We are currently experiencing a slowness while processing flows' execution logs. The execution logs will be delayed to be reflected in the Wevo iPaaS portal but no flows' executions are getting impacted, all flows are properly being executed as their schedules are configured.
- identified Feb 03, 2025, 10:34 AM UTC
The issue has been identified and the team is currently working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 11:30 AM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 12:30 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 01:30 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 02:38 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 03:33 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed.
- identified Feb 03, 2025, 04:33 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.
- identified Feb 03, 2025, 06:23 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.
- identified Feb 03, 2025, 09:32 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.
- identified Feb 03, 2025, 11:38 PM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.
- identified Feb 04, 2025, 12:31 AM UTC
The issue has been identified and the team is still working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flows execution haven't been impacted and are still running even though not reflected in the Wevo iPaaS portal.
- monitoring Feb 04, 2025, 02:04 AM UTC
A fix has been implemented and we are monitoring the results. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible.
- identified Feb 04, 2025, 09:43 AM UTC
We have identified a new delay to process flow's execution logs and the team is already working to normalize the scenario. Please note that the flow execution logs will be delayed till the entire enqueued backlog is completely processed. The flow execution hasn't been impacted and is still running even though not reflected in the Wevo iPaaS portal.
- identified Feb 04, 2025, 01:14 PM UTC
We are continuing to work on a fix for this issue. A maintenance has been started in the Wevo iPaaS Cloud Database. There won't be any data loss during this process or impact during the flow execution.
- monitoring Feb 04, 2025, 02:31 PM UTC
The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.
- monitoring Feb 04, 2025, 03:33 PM UTC
The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.
- monitoring Feb 04, 2025, 05:28 PM UTC
The Wevo iPaaS Cloud Database maintenance is still in progress. Going forward, all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the integration execution is finished. Please note that old execution logs may still be delayed to be visible since they are enqueued for processing as a backlog.
- monitoring Feb 04, 2025, 07:47 PM UTC
The Wevo iPaaS Cloud Database maintenance has been finished and all the new flow's execution logs will be reflected in the Wevo iPaaS portal after the flow execution is finished. We're currently working to process the delayed logs backlog from the past few days and monitoring the environment health.
- resolved Feb 04, 2025, 08:47 PM UTC
This incident has been resolved. All the new flow's execution logs are being reflected in the Wevo iPaaS portal as the integrations are executed. We expect to process the entire backlog in the next 72 hours.