[core] xcom_backend = my_project.xcom_backend.ExclusiveRedisXCom
For true data isolation or to handle sensitive/large data "exclusively" outside the Airflow DB: airflow xcom exclusive
| Issue | Consequence | |-------|--------------| | DB becomes bottleneck | Many large XComs slow down scheduler | | Not designed for streaming | Only final values, not incremental | | No automatic cleanup (unless configured) | XCom rows accumulate | | Cross-DAG XCom is fragile | Requires manual conf passing | [core] xcom_backend = my_project
Tasks interact with XComs through two main methods on the TaskInstance object: airflow xcom exclusive
By default, XCom allows to write to any key, and any task to read from any key. This creates several issues:

I’m Ana Frias and I’m so glad you’re here!
I believe you can make authentic Mexican food wherever you are in the world! I was born and raised in Sonora Mexico, and here I share my recipes inspired by my native country.
“My mission is to share authentic Mexican recipes that anyone can make at home. As a one-person team, I handle everything, from testing and perfecting each recipe to cooking, writing, and photographing, so you can trust that every dish is truly tried and tested.”
Copyright 2015-2025 by Muy Delish/Ana Frias