Hi everyone, After our recent migration to dbt fusion we ran into issue with our source freshness job. for the same I have opened bug issue on elementary repo https://github.com/elementary-data/elementary/issues/2245 Does anyone here could help us with this

Hey @Prat Agrrawal, thank you for bringing this to our attention! Taking a deeper look

thank you

Hi @Prat Agrrawal I spotted the same issue two month ago here I didn't find the fix yet 😕

Hi Kim, I have debugged using Claude and Identified the root cause

crash is in process_freshness_result at the line "unique_id": result_dict.node.unique_id
— dbt-fusion's freshness result objects return None for node in some cases (e.g. sources that
error). A null guard fixes it:

{% if result_dict.node is none or result_dict.node is undefined %}
{% do return(none) %}
{% endif %}

The caller upload_source_freshness also needs to filter none results before passing to
upload_artifacts_to_table.

Currently we have disabled freshness check in elementary

vars:
  elementary:
    disable_freshness_results: true

hopefully @Noya Offer we could patch this soon

We're about to deploy a fix, will share an update soon!

awesome!!