I’m a big fan of the new focus on assets instead of jobs, makes things possible that were quite hard before - that said, what’s the recommended way to “connect” two jobs through assets when they don’t live in the same repo? I can use a sensor, but that doesn’t make it show up in the asset diagram, nor warn me when the upstream changed

You can use the `SourceAsset`function: https://docs.dagster.io/concepts/assets/software-defined-assets#defining-external-asset-dependencies

oh wow, completely missed that one, thanks! 🙂

Hm, my first impulse would be to create a sensor that periodically pings the GraphQL API and alerts if a condition is met, but maybe Dagster offers something that I don’t know about?

Yeah, I think setting up a schedule to check for out of date assets makes sense for this case.

would it be possible to do this for the job itself? <alert if job hasn’t run in 48hours>?

Yep, you could have a schedule that queries for successful runs by job and alert appropriately

nice, thanks!