Hi <!subteam^S08HYBWCF6E>, 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

Hi! Yes, this is a known compatibility issue between Elementary and dbt-fusion. Here's a summary of what's happening and your options: Root Cause When running

dbt source freshness

with dbt-fusion, the

on_run_end

hook crashes because

result.to_dict()

returns

None

for the

node

field on some freshness results. The

process_freshness_result

macro doesn't guard against this. [GitHub issue] Additionally, source freshness results are not reported by dbt-fusion itself, which is a known upstream limitation tracked in dbt-fusion issue #720. [Missing features] Immediate Workaround The most reliable workaround right now is to disable freshness result uploads via an Elementary variable in your `dbt_project.yml`:

vars:   elementary:     disable_freshness_results: true

Elementary's

on_run_end

hook checks this flag before calling

upload_source_freshness()

, so the broken code path is never reached. All other Elementary artifact uploads continue to work normally. [GitHub issue] Other Notes • You can safely remove

source_freshness_run_project_hooks

and

require_generic_test_arguments_property

from your

dbt_project.yml

— these flags have been removed in dbt Fusion. [dbt Fusion integration] • Project-level macro overrides do not work as a workaround in Fusion's strict namespace dispatch —

elementary.macro_name()

calls go directly to the installed package. [GitHub issue] • Elementary's dbt-fusion support is still in beta, so some edge cases like this are expected. [Missing features] The fix (adding null guards in

process_freshness_result

and

flatten_source_freshness

) needs to come from the Elementary package itself. Since you've already opened the GitHub issue, that's the right place to track progress — and the issue notes you're willing to submit a PR, which would be a great contribution! 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.

is this got fixed in latest release ?

Sorry @Prat Agrrawal, I'm not sure what you mean. Please try again. 👋

is this got fixed in latest release of elementary ? @kapa.ai

I'm sorry, but the knowledge sources do not contain enough information to confirm whether this issue has been fully fixed in the latest Elementary release. What the knowledge sources do indicate is: • The bug (GitHub issue #2245) was still open at the time of the last recorded discussion, with Elementary's team acknowledging it and noting a fix was being prepared: "We're about to deploy a fix, will share an update soon!" [Slack thread] • However, no knowledge source confirms that a fix has actually been released yet. Recommended Next Steps 1. Check the GitHub issue directly for the latest status: elementary-data/elementary#2245 2. Check the Elementary release notes to see if the fix appears in a recent version. 3. In the meantime, continue using the workaround:

vars:
  elementary:
    disable_freshness_results: true

[GitHub issue] 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.