we're using the

build_asset_reconciliation_sensor

where we select an asset group. For some reason the created

__ASSET___JOB

looks like it's all assets, including downstream assets in a different group. Is this expected behavior? I was under the impression the job would only be for all downstream assets in the group

Are you referring to

AssetSelection.groups(...).downstream()

? The

downstream

method will select downstream assets that are outside of the existing selection. You could do something like this instead:

AssetSelection.groups(...).downstream() & AssetSelection.groups(...)

No our definition is as follows:

build_asset_reconciliation_sensor(
        name="update_training_model_assets_sensor",
        asset_selection=AssetSelection.groups("training_model"),
    ),

ahhh I see. So under the hood, dagster builds internal jobs containing all of the assets in the repository in order to allow you to add assets to a

Definitions

object without defining a job containing those assets. Similarly, these internal jobs enable you to select and kick off materializations via Dagit without having a job defined. The reconciliation sensor is referencing the internal job, to which it'll apply the asset selection provided to the reconciliation sensor. So I think you'll still get the behavior that you expect, I think it's probably just a little bit weird of a UI experience.