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.
Posted May 29, 2025 - 19:47 UTC
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
Posted May 29, 2025 - 14:37 UTC
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
Posted May 29, 2025 - 14:00 UTC
Update
We are continuing to investigate this issue.
Posted May 29, 2025 - 13:58 UTC
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
Posted May 29, 2025 - 13:38 UTC
This incident affected: Sources (Amazon S3, Microsoft Azure Blob Storage).