@Scout which table does store data of the schedules run?

The data for schedule runs in Dagster is stored in the

job_ticks

table within the Dagster instance's metadata database. This table stores information for each tick of a schedule, which includes whether the schedule resulted in a run being launched, skipped, or failed, along with other metadata about the tick. The

job_ticks

table is part of the system that manages the execution and tracking of schedules in Dagster.

@Scout what is the selector_id in table job_ticks for?

The

selector_id

in the

job_ticks

table is used to associate a tick with a specific schedule or sensor within the Dagster instance. Each schedule or sensor has a unique identifier, and the

selector_id

is a reference to this identifier. When a tick is recorded in the

job_ticks

table, the

selector_id

helps to identify which schedule or sensor the tick is associated with, allowing you to query and filter the tick data based on the specific schedule or sensor. This is useful for tracking the execution history and status of individual schedules or sensors over time.

@Allison Stuckey_