RNHTTR opened a new issue, #33078:
URL: https://github.com/apache/airflow/issues/33078

   ### Apache Airflow version
   
   2.6.3
   
   ### What happened
   
   Consider the following DAG:
   
   ```python
   from pendulum import datetime
   
   from airflow.decorators import (
       dag,
       task,
   )
   from airflow.exceptions import AirflowSkipException
   
   
   @dag(
       schedule="@daily",
       start_date=datetime(2023, 1, 1),
       catchup=False,
       default_args={
           "retries": 2,
       },
       tags=["example"],
   )
   def trigger_rule_mapped_task_bug():
       @task
       def run_me():
           return [1]
   
       @task
       def skip_me():
           raise AirflowSkipException
   
       @task(trigger_rule="none_failed_min_one_success")
       def map_me(x, y):
           print(x)
   
       map_me.expand(x=run_me(), y=skip_me())
   
   
   trigger_rule_mapped_task_bug()
   ```
   
   The task `map_me` is marked as `upstream_failed` for both the `all_done` and 
`none_failed_min_one_success` trigger rules.
   
   ### What you think should happen instead
   
   I would expect `map_me` to execute for both `all_done` and 
`none_failed_min_one_success` as the `trigger_rule`.
   
   ### How to reproduce
   
   Use the above DAG to reproduce.
   
   ### Operating System
   
   Debian GNU/Linux 11 (bullseye)
   
   ### Versions of Apache Airflow Providers
   
   n/a
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   LocalExecutor using Astro CLI
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to