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

dagster

Hey :wave: We have a job that is mainly triggered by a sensor that detects if there's new or changed data. We want to ensure that the job runs at least once per day, regardless of data changes. To achieve this we have a setup a schedule for the job that runs once per day but we'd want to skip the scheduled run if there has been a successful run on the same date. As a solution I found this <https://github.com/dagster-io/dagster/discussions/8414> where we'd pull run records from the context using `context.instance.get_run_records` . What do you think of this? What other options do we have? Thanks :slightly_smiling_face:

The GraphQL API <https://docs.dagster.io/concepts/webserver/graphql> could also be used here. Would this be a more stable option? The context.get_run_records is listed as an internal functionality and therefore subject to change.

hi <@U02GHV7U3H8>! That solution is what I'd recommend, and is the most direct way to answer "are there any successful runs for this job on this date". `get_run_records` is used heavily internally and is unlikely to change in any significant way.

Thanks for the confirmation <@U01J51Y6B9D> :) We'll go with that