GitHub user pykenny edited a comment on the discussion: Dynamic mapped tasks group arguments are interpreted as MappedArgument when provided to classic operators
Earlier I shared my [thoughts](https://github.com/apache/airflow/discussions/40728#discussioncomment-12100714) on the reply thread, and I think this kind of confusion on writing decorated task group often happens because unlike tasks, task groups are just a set of layered prefixes attached to task ID mainly used for filtering task subset out from a DAG, and that's only why XComs/TaskFlow only work on task level. Making the proposed case work implies redesign on DAG model is needed to make XCom communication possible at group level. GitHub link: https://github.com/apache/airflow/discussions/40728#discussioncomment-12101338 ---- This is an automatically sent email for commits@airflow.apache.org. To unsubscribe, please send an email to: commits-unsubscr...@airflow.apache.org
