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, instead of a task-like entity having relation with all its underlying task entities. And that's also why XComs/TaskFlow only work on task level, but not for task groups. Making the proposed case work implies redesigning DAG model is needed, in order to make XCom communication possible on task groups. 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
