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

dagster

:wave: When we’ve moved over to the dagster-dbt 0.19.4 we’ve started experiencing an issue where the jobs that contain assets completely lost the `materialize` /launch button on the overview pages making it so that we’re unable to run the tasks at all.
eg. Has anyone else experienced the issue ?

update now i think this might be due to asset dependency.
If i try to materialize solely intermediate group for example it doesn’t work.
```dbt_build_asset_int_stage_job = define_asset_job(
    "dbt_models_build_int_and_stage",
    selection=(
        AssetSelection.groups(DBT_INTERMEDIATE_GROUP_NAME)
)
)```


but the moment i specify .upstream assets as well
```dbt_build_asset_int_stage_job = define_asset_job(
    "dbt_models_build_int_and_stage",
    selection=(
        AssetSelection.groups(DBT_INTERMEDIATE_GROUP_NAME).upstream()
    )
)```
the job shows the materialize button, it almost seems as it needs the ‘full lineage’ to allow you to materialize now.

If anyone could clear this up, it would be highly appreciated as it’s breaking our workflows now