DianaHov commented on issue #44336: URL: https://github.com/apache/airflow/issues/44336#issuecomment-5736252850
Thanks for picking this up so quickly, appreciate it. The timetable route was actually where I started. What stopped me was that `next_dagrun_info()` has no visibility of current runs, and going to the DB from there disrupted the scheduler session - that's what pushed me towards a DAG-level param instead, rather than any preference for one over the other. So if an extension point closes that gap, it would cover our case. Either way this is something we really need on our side, so I'd like to see it through. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
