GitHub user apmechev edited a comment on the discussion: "XCom not found" error thrown by EMR Sensors after Airflow 3.0
Hi, thanks for the reply! We're using the default XCom Backend (database). Here are all the Xcoms for a task that raised the error. It has the `_link_*` xcoms pushed (with an empty value). I'm not sure where it's being pushed from as I don't see those keys in our code. I do see it eventually coming from [here](https://github.com/apache/airflow/blob/bf34806f083ef075a1c23a323a77f2a022bba5cb/task-sdk/src/airflow/sdk/bases/operatorlink.py#L56) though. LMK if I can provide any more context! ``` airflow=> select * from xcom where dag_run_id=640179 and task_id='ycp-reporting.check_steps'; dag_run_id | task_id | key | value | timestamp | dag_id | run_id | map_index ------------+---------------------------+----------------------+-------+-------------------------------+----------------------------+--------------------------------------+----------- 640179 | ycp-reporting.check_steps | _link_EmrClusterLink | "" | 2025-06-23 09:17:45.268368+00 | ycp-reporting-pipeline-dev | scheduled__2025-06-23T09:00:00+00:00 | -1 640179 | ycp-reporting.check_steps | _link_EmrLogsLink | "" | 2025-06-23 09:17:45.318799+00 | ycp-reporting-pipeline-dev | scheduled__2025-06-23T09:00:00+00:00 | -1 ``` Error log: <details> ``` { "run_id": "scheduled__2025-06-23T09:00:00+00:00", "status_code": 404, "level": "error", "map_index": -1, "task_id": "ycp-reporting.check_steps", "dag_id": "ycp-reporting-pipeline-dev", "detail": { "detail": { "reason": "not_found", "message": "XCom with key='emr_logs' map_index=-1 not found for task 'ycp-reporting.check_steps' in DAG run 'scheduled__2025-06-23T09:00:00+00:00' of 'ycp-reporting-pipeline-dev'" } }, "event": "XCom not found", "key": "emr_logs", "timestamp": "2025-06-23T09:17:45.301904Z", "logger": "airflow.sdk.api.client" } ``` </details> GitHub link: https://github.com/apache/airflow/discussions/51652#discussioncomment-13549402 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
