Hey Dagster team, I'm running into an issue with having dependencies across 2 jobs that run on 2 different schedules.
Job A runs hourly, and Job B, which has dependencies on assets in Job A, runs on a daily schedule. The dependencies are respected when doing manual runs with all downstream assets, but when something in a scheduled run of Job A fails, the downstream assets in the scheduled Job B still run. Is this expected?
The recommended approach seems to be to use asset sensors as mentioned here:
https://github.com/dagster-io/dagster/discussions/8484
Is there a way to combine sensors with a schedule? i.e. skip assets in Job B if their upstream dependency in Job A failed to materialize. Or another approach I should consider?
I've also looked into auto-materialization which seems like a better approach to adopt later, but I'm looking for something I can do to "glue" the 2 schedules together better in the interim.