The cloud-native orchestrator for the whole development lifecycle, with integrated lineage and observability.

dagster

image.png

is this a bug with auto-materialization and dataversions, or am I misunderstanding something? I have a downstream asset showing that there are new dataversions for of upstream assets. however, no materializations have been launched since 7/21 until I just manually ran one

upstream asset is an observable source asset, downstream is a dbt asset with an eager policy

in case you missed it just like I did, have you explicitly turned automaterialization on?
<https://docs.dagster.io/concepts/assets/asset-auto-execution#turning-on-auto-materializing>