xcom_pull called via AirflowGUI can't be set include_prior_dates=True

[kawatatatsuya]

Apache Airflow version

3.1.0

If "Other Airflow 2/3 version" selected, which one?

No response

What happened?

I tried to retrieve a value that was pushed to XCom in DAG A from DAG B.
When I intentionally changed the scheduled execution times of DAG A and DAG B and ran them, I was unable to retrieve the XCom value from DAG B.
After making a small modification to the source code, I found that the parameter include_prior_dates=True was not being passed, and in all calls made from the Airflow GUI, this value was set to False, which caused the return value not to be retrieved.

What you think should happen instead?

That the value of include_prior_dates is correctly passed.

How to reproduce

Start the attached DAG_A, and then start DAG_B from the Airflow GUI.
DAG_B.py
DAG_A.py

Operating System

Ubuntu 22.04.4 LTS

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

uv 0.9.3
Python 3.10.7

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[amoghrajesh]

@kawatatatsuya thanks for opening the issue, do you happen to recall what the situation was like for Airflow 2?

(I could check but on Tuesday)

[kawatatatsuya]

@amoghrajesh
Sorry, I found this while investigating version 3 features, so I didn’t use it in version 2. I’ll also look into version 2. I don’t have much time on weekdays, so it might take me a little while.

[amoghrajesh]

Sure take your time. I will add it to the next patch level release milestone. Once you have an update, we could work together towards completing it.

[kawatatatsuya]

@amoghrajesh
Sorry for the late reply!
After investigating version 2, I found that it was working without any issues. The results of my investigation are as follows.

Condition	Airflow 2	Airflow 3	Notes
dag_a and dag_b start with the same schedule	✅	✅	-
dag_a and dag_b have different schedules and include_prior_dates=False	✅	✅	-
dag_a and dag_b have different schedules and include_prior_dates=True	✅	❌	In v3, dag_b cannot receive XCom
dag_b is triggered manually and include_prior_dates=False	✅	✅	-
dag_b is triggered manually and include_prior_dates=True	✅	❌	In v3, dag_b cannot receive XCom

This is my first contribution to an open-source project, so I would like to fix it through to the end if possible.
However, I tried adding a log to xcom_pull in airflow/models/taskinstance.py as an experiment, but it hasn’t been output to the terminal or under AIRFLOW_HOME/logs, so I’m still troubleshooting.
Do you have a solution for this?

Thank you!

[kawatatatsuya]

@amoghrajesh
I was thinking of working on this issue, but is it the same as what is being addressed in the following PR?
#53809

[amoghrajesh]

@kawatatatsuya that was fixed for 3.0.5. Are you seeing the issue even now with 3.1?

[kawatatatsuya]

@amoghrajesh
Thank you. It seems the version I checked was 3.0.3, so it was outdated.
Since I believe this has already been fixed, I’ll mark it as completed.