luc-pimentel opened a new pull request, #73952: URL: https://github.com/apache/airflow/pull/73952
`[scheduler] use_job_schedule = False` is documented as turning off cron scheduling, but it also stopped asset-triggered Dag runs. The asset event stayed queued and no run was created. With this change, asset-triggered runs are created even when the option is off. In that case the scheduler only picks Dags with queued asset events, so Dags that are due on a schedule don't use up `max_dagruns_to_create_per_loop`. I also updated the tip in `best-practices.rst` that said the option stops all new runs. Tested on 3.3.2 and main with `airflow standalone` and the Dag from the issue, posting an asset event through the REST API: | `use_job_schedule` | Before | With this change | | --- | --- | --- | | `True` | run created | run created | | `False` | no run, event stays queued | run created | With the option off, cron Dags still get no runs and manual runs still work. Three of the four new tests fail without this change. #62931 and #67764 tried a similar fix and were closed before merging. closes: #62929 --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Opus 5.5) Generated-by: Claude Code (Opus 5.5) following [the guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions) -- 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]
