devgonvarun opened a new issue, #70173:
URL: https://github.com/apache/airflow/issues/70173
### Under which category would you file this issue?
Airflow Core
### Apache Airflow version
3.2.2, 3.3.0
### What happened and how to reproduce it?
Try running this simple dag pair for cross dag xcom transfer. The
cross_dag_xcom_downstream dag correctly receives the xcom value at airflow
v3.1.7 but receives None in airflow v3.2x and v3.3.0. The
cross_dag_xcom_upstream correctly creates an xcom entry its just that the
cross_dag_xcom_downstream is not able to access it.
`
from airflow.sdk import dag, task
@dag()
def cross_dag_xcom_upstream():
@task
def push_to_xcom():
return "Hello!"
push_to_xcom()
cross_dag_xcom_upstream()
@dag()
def cross_dag_xcom_downstream():
@task
def pull_from_xcom(**context):
print("The context task instance is", context["task_instance"])
my_data = context["task_instance"].xcom_pull(
dag_id="cross_dag_xcom_upstream",
task_ids="push_to_xcom",
key="return_value",
include_prior_dates=True,
)
return my_data
pull_from_xcom()
cross_dag_xcom_downstream()`
### What you think should happen instead?
The downstream dag should receive the xcom.
### Operating System
_No response_
### Deployment
_No response_
### Apache Airflow Provider(s)
_No response_
### Versions of Apache Airflow Providers
_No response_
### Official Helm Chart version
Not Applicable
### Kubernetes Version
_No response_
### Helm Chart configuration
_No response_
### Docker Image customizations
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] 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]
