Short clarification question about the

run_key

in Schedule evaluations: the docs say “For sensors, ensures that only one run is created per run key across all sensor evaluations. For schedules, ensures that one run is created per tick, across failure recoveries.” Does this mean separate ticks of the same schedule returning `RunRequest`s with the same

run_key

would result in the runs being launched?

Hey Vinnie - that's right, a tick at 10:00 and a tick at 11:00 with the same run key would still produce two runs - the run key will disambiguate between multiple runs produced from the same tick

Gotcha, thanks.