Rivery incident
Boomi - Process Reporting Document Metadata Degraded - Resolved
Rivery experienced a minor incident on October 25, 2025 affecting Process Reporting Document Metadata, lasting 6h 53m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating Oct 25, 2025, 11:46 AM UTC
The Boomi Process Reporting Document Metadata are currently operating at a higher-than-normal latency. You may experience degraded performance during this time. Our engineering team is investigating the issue and we will provide an update once we have more information. We apologize for any inconvenience this incident has caused.
- investigating Oct 25, 2025, 12:17 PM UTC
We are continuing to investigate this issue.
- investigating Oct 25, 2025, 01:21 PM UTC
Our engineering team continue investigating the issue and we will provide an update once we have more information. We apologize for any inconvenience this incident has caused.
- investigating Oct 25, 2025, 02:24 PM UTC
Our engineering team continues investigating the issue and we will provide an update once we have more information. We apologize for any inconvenience this incident has caused.
- identified Oct 25, 2025, 02:27 PM UTC
We have identified the cause of the degraded performance you may have experienced on the Process Reporting Document Metadata. Our engineering team is working to resolve the issue and we will provide an update once the issue is resolved. We apologize for any inconvenience this incident may have caused.
- monitoring Oct 25, 2025, 03:17 PM UTC
Our engineering team implemented corrective actions to resolve the issues with the Boomi Process Reporting Document Metadata. We are monitoring the situation to ensure continued availability while our processes continue to work through the backlog of messages.
- resolved Oct 25, 2025, 06:40 PM UTC
Our engineering team has corrected the issue and Boomi Process Reporting Document Metadata is operating as expected for all new executions. Please note that users may still experience delays in updates to Process Reporting for the affected period as we work through the backlog of messages.