Add source freshness status to sources table

[emilyjia]

Thanks for the updates to version 1.0.0.
Is there a way to access the status of source freshness tests in the existing models? I see the freshness criteria in the sources table, but not the freshness status.
Alternatively, is it possible to add the status property (from sources.json) to the sources table?

[NiallRees]

Hey @emilyjia - this is not possible today while we wait for dbt-labs/dbt#5609 but thank you for bringing it up!

[steveh-101]

hi @NiallRees

I was looking at this as we also want to use the freshness status.

status is present in sources.yml, after dbt source freshness - and it does not get overwritten after dbt run

but when we upload the freshness only has criteria and no freshness status. Could we not add column for status if the key is present it is there, otherwise null? Is there a reason to wait for the issue mentioned?

[glsdown]

Hi @RudeB0y apologies for the delay in getting back to you here. dbt artifacts relies on the run result object provided via the on-run-end hook rather than the files created themselves. This doesn't include the source freshness status though unfortunately. The PR that Niall has referenced aims to make this data available though, which is why we are unable to use it until that has been implemented.

[zs-gpillai]

is this feature implemented or are there any timelines on this ?
Since we are also looking for the same.

[VDFaller]

Just mentioning that dbt-labs/dbt#5609 is merged.

[aryan-tmg]

Just pinging... Any update on this feature? dbt-labs/dbt#5609 is merged

[martindlarsson]

This would be great. Any timeline when it can get implemented?

[karenderer]

Coming here to comment that I'm looking forward to this being implemented as well!

[gmarinho-convex]

Hey @dpguthrie, just reaching out to know your plans for the PR opened. Is there any way I can help you out?

[joao-canutto]

Looking forward for this implementation as well!

[VDFaller]

@NiallRees, @glsdown , do you think that the upstream label should be removed so at least this isn't automatically ignored?

[AdamAtValtech]

Hi - It looks like the last activity on this issue's PR ( #437 ) was on 26 June 2025. I want to thank @dpguthrie as he has clearly put a lot of hard work on this PR. However, I see that it is currently failing at the integration testing steps for SQL Server, BigQuery, and Trino.

Would someone be in a position to provide an update on where this deliverable now stands?

I also echo the suggestion of @VDFaller that, unless the upstream label on this issue is in reference to the current blockers on the linked PR, it should probably be removed from this issue.

Thanks in advance!

[dennysrega1ado]

Just checking—has anyone started working on this issue, or has it been put on hold?