This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git
The following commit(s) were added to refs/heads/main by this push:
new ddf21c71e1c Clarify that XComs can't be used to persist state accross
retries or poke. (#57577)
ddf21c71e1c is described below
commit ddf21c71e1c89e8a15a01421e2d472998290dbe0
Author: Desdroid <[email protected]>
AuthorDate: Sat Nov 1 16:44:37 2025 +0100
Clarify that XComs can't be used to persist state accross retries or poke.
(#57577)
---
airflow-core/docs/core-concepts/xcoms.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/airflow-core/docs/core-concepts/xcoms.rst
b/airflow-core/docs/core-concepts/xcoms.rst
index aa89050261e..13b77af2737 100644
--- a/airflow-core/docs/core-concepts/xcoms.rst
+++ b/airflow-core/docs/core-concepts/xcoms.rst
@@ -78,7 +78,7 @@ An example of pushing multiple XComs and pulling them
individually:
.. note::
- If the first task run is not succeeded then on every retry task XComs will
be cleared to make the task run idempotent.
+ If the first task was not successful then on every retry task XComs will be
cleared to make the task run idempotent. XComs therefore can't be used to
persist state across task retries or :doc:`./sensors` poke.
Object Storage XCom Backend
