ldacey commented on issue #53593:
URL: https://github.com/apache/airflow/issues/53593#issuecomment-3102827803
I didn't originally when I first encountered the issue but I added it as
part of the troubleshooting and it is still in place.
```
- name: AIRFLOW__CORE__XCOM_BACKEND
value:
"airflow.providers.common.io.xcom.backend.XComObjectStorageBackend"
- name: AIRFLOW__COMMON_IO__XCOM_OBJECTSTORAGE_PATH
value: "gs://conn-id@airflow_bucket/xcom"
- name: AIRFLOW__COMMON_IO__XCOM_OBJECTSTORAGE_THRESHOLD
value: "1000"
```
Added it on 07/20 but that is when I downgraded to 3.0.2 as well. I do not
think this was the fix because I got XComs to work locally with Docker compose
before I updated the helm chart (no xcom_backend in docker).
```
Date: Sun Jul 20 07:31:06 2025 +0800
fix(airflow): downgrade airflow to 3.0.2 and enable xcom_backend
```
Timestamp of when I upgraded to 3.0.3 lines up with the logs above where the
DAGs began pulling since dag_start instead of the XCom value as well:
```
defaultAirflowTag: 3.0.3
defaultAirflowTag: 3.0.2
Date: Fri Jul 18 02:45:14 2025 +0800
ci(airflow): bump to 3.0.3
```
--
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]
