I see where the confusion is coming from, it is my mistake. Sorry about that.
To clarify, I am taking about the use case where the key parameter is passed but the task_ids parameter is not or it is None. -----Original Message----- From: Foldvari, Gyorgy via dev <[email protected]> Sent: Wednesday, April 15, 2026 13:42 To: [email protected] Cc: Foldvari, Gyorgy <[email protected]> Subject: RE: Re: [DISCUSS] Reconsidering `xcom_pull(task_ids=None)` behavior change in Airflow 3 CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. The original behavior is to return the most recent value put by any upstream task of the same run. Not all the values, only the recent one. Supposing that there are multiple tasks pushing values to XCom in this order: Task1: ti.xcom_push(key="example", value=1) Task2: ti.xcom_push(key="example", value=2) Task3: ti.xcom_push(key="example", value=3) Then in a downstream task ti.comm_pull(key="example") returns 3. I do not propose to change this behavior. On 2026/04/14 16:09:05 Daniel Standish via dev wrote: > So the behavior before would be that it would return all xcom values > that were emitted from the present run? > ________________________________ Information regarding MSCI's processing of personal data may be found at www.msci.com/privacy-pledge. This email message and any attachments are for the sole use of the intended recipients and may contain proprietary and/or confidential information which may be privileged or otherwise protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. All rights and remedies are reserved. If you are not an intended recipient, please contact the sender by reply email and destroy the original message and any copies of the message as well as any attachments to the original message. Local registered entity information: https://www.msci.com/local-registered-entities --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
