Fivetran: Some dbt Core Transformations are failing with no logs
Incident
Report for Fivetran
Resolved
Incident Summary:
This incident has been fully resolved. Instance rates have returned to normal, and logs are now correctly showing failed transformation runs.
Description:
DBT logs were not appearing for failed transformation jobs.
Timeline:
The issue started on Aug 04, 2025, at 12:00 UTC and was resolved on Aug 06, 2025, at 00:45 UTC
Cause:
The issue was introduced by new logic related to auto-pausing failing jobs, which contained faulty conditional handling.
Resolution:
Corrected logic was deployed, restoring proper logging of failed runs.
Note: Transformation execution was never impacted. The issue only affected the saving and display of failure causes and results.
This incident has been fully resolved. Instance rates have returned to normal, and logs are now correctly showing failed transformation runs.
Description:
DBT logs were not appearing for failed transformation jobs.
Timeline:
The issue started on Aug 04, 2025, at 12:00 UTC and was resolved on Aug 06, 2025, at 00:45 UTC
Cause:
The issue was introduced by new logic related to auto-pausing failing jobs, which contained faulty conditional handling.
Resolution:
Corrected logic was deployed, restoring proper logging of failed runs.
Note: Transformation execution was never impacted. The issue only affected the saving and display of failure causes and results.
Update
Corrected logic was deployed, restoring proper logging of failed runs.
Monitoring
A fix has been implemented and we are monitoring the results.
Update
The issue does not impact the actual execution of transformations.
Instead, it affects the handling of failed transformation runs, specifically the saving of results and related logs.
When a transformation run fails, we are currently unable to correctly store the failure result, which is why the expected logs or error messages are not visible.
However, this does not interfere with the transformation process itself.
Instead, it affects the handling of failed transformation runs, specifically the saving of results and related logs.
When a transformation run fails, we are currently unable to correctly store the failure result, which is why the expected logs or error messages are not visible.
However, this does not interfere with the transformation process itself.
Identified
The issue has been identified and we are working to resolve it.