Team as I look at the flyte schedule it appears futuristic only. Is there a handy way to achieve catchup jobs and set dependency on past executions like we do in airflow.

I don't think there's a way right now in Flyte to control the catchup behavior (enabled by default) cc @Prafulla Mahindrakar

thats right catch up behavior is enabled by default. If there is downtime for the scheduler pods, the catchup routine checks for any missed schedules and executes them . coming to question of setting a dependency on past execution, this is not something supported directly by scheduler but you can potentially use sensors https://docs.flyte.org/en/latest/deployment/agents/sensor.html