Rivery Status

Resolved: We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

A limited number of River runs were impacted by the following error: TypeError: can't compare datetime.datetime to datetime.date

The root cause was identified and a fix was successfully deployed. Since then, no further failures have been observed. System performance has remained stable during the monitoring period.

This incident is now considered fully resolved. Thank you for your patience and understanding.

For any further questions please contact our Support Team.

Monitoring: We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

Incident start: May 28, 2025, at 16:00 IST (13:00 UTC)

Incident resolved: May 29, 2025, at 17:30 IST (14:30 UTC)

The issue resulted in a limited number of River runs failing with the error: TypeError: can't compare datetime.datetime to datetime.date

We are currently monitoring the system to ensure full stability. No further failures have been observed since the fix was deployed.

We will post a final update once the incident is fully resolved.

Thank you for your patience. Data integration (Rivery) suport team

Identified: We have identified that the issue is impacting Rivers with S3 and Azure Blob as their data sources. These Rivers may fail with the following error: TypeError: can't compare datetime.datetime to datetime.date

We are working on a fix and will update as progress is made.

Best Regards Data integration (Rivery) suport team

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating an issue causing failures in a minor portion of River runs.

The error message observed is: "TypeError: can't compare datetime.datetime to datetime.date"

Our team is actively working to pinpoint the exact configuration that is leading to these failures. Most River runs continue to operate normally.

We will provide further updates as soon as more information becomes available.

Thank you for your patience. Data integration (Rivery) suport team

Resolved: After monitoring we see ECB Currency Rate endpoint is now fully operational. The earlier disruption was due to an issue with the upstream source API and all associated data pipelines ("rivers") are running as expected.

Should you experience any further issues or have questions, please contact our Boomi support team and we will be happy to assist you! Thank you for your patience and continued trust.

Monitoring: The ECB Currency Rate endpoint is now fully operational. The earlier disruption was due to an issue with the upstream API on the source endpoint. All data pipelines ("rivers") are running successfully at this time.

We will continue to monitor the situation to ensure continued stability. Thank you for your patience.

Investigating: Our team is continuing to investigate the issue affecting ECB currency rate rivers. At this time, our findings suggest the issue is originating from the ECB's API itself. We are monitoring the situation closely and will provide further updates as more information becomes available.

Investigating: We are currently investigating an issue causing ECB (European Central Bank) currency rate connectors to fail with a 404 Not Found error. Our team is looking into whether the source of the issue is with the ECB API.

We will share updates as soon as we have more information.

Thank you for your patience.

Resolved: We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

A limited number of River runs were impacted by the following error: TypeError: can't compare datetime.datetime to datetime.date

The root cause was identified and a fix was successfully deployed. Since then, no further failures have been observed. System performance has remained stable during the monitoring period.

This incident is now considered fully resolved. Thank you for your patience and understanding.

For any further questions please contact our Support Team.

Monitoring: We have deployed a fix for the issue that was causing failures in some Rivers using S3 and Azure Blob data sources.

Incident start: May 28, 2025, at 16:00 IST (13:00 UTC)

Incident resolved: May 29, 2025, at 17:30 IST (14:30 UTC)

The issue resulted in a limited number of River runs failing with the error: TypeError: can't compare datetime.datetime to datetime.date

We are currently monitoring the system to ensure full stability. No further failures have been observed since the fix was deployed.

We will post a final update once the incident is fully resolved.

Thank you for your patience. Data integration (Rivery) suport team

Identified: We have identified that the issue is impacting Rivers with S3 and Azure Blob as their data sources. These Rivers may fail with the following error: TypeError: can't compare datetime.datetime to datetime.date

We are working on a fix and will update as progress is made.

Best Regards Data integration (Rivery) suport team

Investigating: We are continuing to investigate this issue.

Investigating: We are currently investigating an issue causing failures in a minor portion of River runs.

The error message observed is: "TypeError: can't compare datetime.datetime to datetime.date"

Our team is actively working to pinpoint the exact configuration that is leading to these failures. Most River runs continue to operate normally.

We will provide further updates as soon as more information becomes available.

Thank you for your patience. Data integration (Rivery) suport team