Lee-W opened a new issue, #65760: URL: https://github.com/apache/airflow/issues/65760
### Body ### What Protect the scheduler from a misbehaving `to_downstream` that returns thousands of keys (e.g., a runtime query returning far more elements than expected). Provide two layers: 1. an author-level `max_fan_out` knob tuned per Dag 2. a scheduler-enforced hard backstop that applies regardless of author intent ### Open question Default values for each layer, and behavior when exceeded — fail the upstream run, fail only the scheduling attempt, or truncate with a warning? ### Related #65654, #44146 ### Committer - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project. -- 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]
