Do not ignore include_prior_dates in xcom_pull when map_indexes is not specified

[amoghrajesh]

closes: #53593

Problem

The include_prior_dates parameter in xcom_pull() was being completely ignored when map_indexes was not explicitly specified (default NOTSET case). This caused XComs from previous DAG runs to not be retrieved even when include_prior_dates=True was passed.

Example:

@task def xcom_task(ti): # This should find XComs from previous runs, but didn't work data_xcom = ti.xcom_pull(key="test_key", include_prior_dates=True) if data_xcom: print(f'XCom pulled. Value: {data_xcom}') else: print(f'XCom not found') # Always printed this, even when XCom existed from previous run ti.xcom_push(key="test_key", value=' - xcom value - ') 

Expected behavior: 2nd run should print "XCom pulled. Value: - xcom value -"

Why?

After #51568, the xcom_pull() method has with two code paths:

• When map_indexes=NOTSET → use XCom.get_all() to get all the xcoms for all map indexes
• When map_indexes explicitly specified → use XCom.get_one()

After introducing path 1, there could be cases when include_prior_dates is passed but XCom.get_all path is chosen, which ignores that parameter entirely.

The bug occurred because:
XCom.get_all() didn't support the include_prior_dates parameter
The first path was always chosen when map_indexes wasn't specified
include_prior_dates was silently ignored and never passed through the communication chain

Solution

Extended the first path to support include_prior_dates by threading the parameter through the entire communication chain:

• XCom.get_all() - Added include_prior_dates: bool = False parameter
• GetXComSequenceSlice - Added include_prior_dates: bool = False field
• Supervisor - Updated to pass include_prior_dates to API client
• API Client - Updated get_sequence_slice() to accept and pass parameter
• API Server - Updated get_mapped_xcom_by_slice() to use parameter in database query
• Task Runner - Updated to pass include_prior_dates to XCom.get_all()

Testing

DAG:
Min repro dag from the issue:

from datetime import datetime, timedelta from airflow.sdk import dag, task @dag( schedule=timedelta(seconds=60), start_date=datetime(2025, 7, 22), catchup=False, max_active_runs=1 ) def xcom_test(): @task def xcom_task(ti): data_xcom = ti.xcom_pull(key=f"test_key", include_prior_dates=True) if data_xcom: print(f'XCom pulled. Value: {data_xcom}') else: print(f'XCom not found') ti.xcom_push(key=f"test_key", value=' - xcom value - ') xcom_task() xcom_test() 

Before

Run 1:

Run 2 and later:

After

Run 1:

Run 2:

Run 3:

No Cadywn migration needed - This is a backward compatible API change with change only in parameters and no request / response models have changed.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[github-actions]

Backport failed to create: v3-0-test. View the failure log Run details

Status	Branch	Result
❌	v3-0-test

You can attempt to backport this manually by running:

cherry_picker 2a2d3e1 v3-0-test

This should apply the commit to the v3-0-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

[amoghrajesh]

This likely needs multiple other PRs to be cherry picked