Here you will find real-time information on Jitterbit system status. Click Subscribe to Notifications to receive email, text message, Slack, or webhook notifications.
Jitterbit is vigilant at applying safe and secure integration processes. We use strict security measures to protect our customers’ valuable information, and constantly evaluate and improve our systems and processes to keep abreast of the latest security demands.
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.
Posted Feb 04, 2025 - 20:47 UTC
Update
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.
Posted Feb 04, 2025 - 19:47 UTC
Update
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.
Posted Feb 04, 2025 - 17:28 UTC
Update
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.
Posted Feb 04, 2025 - 15:33 UTC
Monitoring
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.
Posted Feb 04, 2025 - 14:31 UTC
Update
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.
Posted Feb 04, 2025 - 13:14 UTC
Identified
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.
Posted Feb 04, 2025 - 09:43 UTC
Monitoring
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.
Posted Feb 04, 2025 - 02:04 UTC
Update
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.
Posted Feb 04, 2025 - 00:31 UTC
Update
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.
Posted Feb 03, 2025 - 23:38 UTC
Update
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.
Posted Feb 03, 2025 - 21:32 UTC
Update
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.
Posted Feb 03, 2025 - 18:23 UTC
Update
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.
Posted Feb 03, 2025 - 16:33 UTC
Update
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.
Posted Feb 03, 2025 - 15:33 UTC
Update
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.
Posted Feb 03, 2025 - 14:38 UTC
Update
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.
Posted Feb 03, 2025 - 13:30 UTC
Update
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.
Posted Feb 03, 2025 - 12:30 UTC
Update
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.
Posted Feb 03, 2025 - 11:30 UTC
Identified
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.
Posted Feb 03, 2025 - 10:34 UTC
Investigating
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.
Posted Feb 03, 2025 - 10:22 UTC
This incident affected: LATAM Wevo iPaaS (Runtime Flow Logs).