[core] xcom_backend = my_project.xcom_backend.ExclusiveRedisXCom Or use the built-in Redis backend (install apache-airflow-providers-redis ):
Enter —a feature designed to enforce stricter boundaries, improve performance, and make your DAGs more predictable. But what exactly is it? How do you enable it? And is it right for your team? airflow xcom exclusive
Exclusive mode shines when data volume or concurrency is high. Pattern 1: XCom as Immutable Log Push only once, never overwrite a key. Use execution_date + task_id as part of the key. Enable exclusive mode to prevent accidental re-push. Pattern 2: Conditional XCom Bridges Use ShortCircuitOperator with exclusive mode to stop downstream tasks if a certain key’s value doesn’t meet a threshold: [core] xcom_backend = my_project
with DAG( "fraud_detection", xcom_exclusive_keys= "fetch_transactions": ["raw_txns"], "validate": ["valid_txns", "error_count"], "feature_engineering": ["features"], "fraud_model": ["score"], , xcom_backend="myapp.xcom.S3ExclusiveXCom", ) as dag: And is it right for your team