rawwar opened a new issue, #56701:
URL: https://github.com/apache/airflow/issues/56701
### Apache Airflow version
Other Airflow 2/3 version (please specify below)
### If "Other Airflow 2/3 version" selected, which one?
3.0
### What happened?
At the time of creating this issue, I haven't looked into how to reproduce
the issue. But, I noticed below error in dag-processor logs:
```
--- Supervised process Last chance exception handler ---
Traceback (most recent call last):
File
"/usr/local/lib/python3.12/site-packages/airflow/sdk/execution_time/supervisor.py",
line 387, in _fork_main
target()
File
"/usr/local/lib/python3.12/site-packages/airflow/dag_processing/processor.py",
line 172, in _parse_file_entrypoint
result = _parse_file(msg, log)
^^^^^^^^^^^^^^^^^^^^^
File
"/usr/local/lib/python3.12/site-packages/airflow/dag_processing/processor.py",
line 188, in _parse_file
_execute_callbacks(bag, msg.callback_requests, log)
File
"/usr/local/lib/python3.12/site-packages/airflow/dag_processing/processor.py",
line 228, in _execute_callbacks
_execute_task_callbacks(dagbag, request, log)
File
"/usr/local/lib/python3.12/site-packages/airflow/dag_processing/processor.py",
line 289, in _execute_task_callbacks
dag = dagbag.dags[request.ti.dag_id]
~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^
KeyError: '<redacted_dag_id>'
```
### What you think should happen instead?
If its possible that `request.ti.dag_id` cannot be in dagbag.dags, we might
need to use `get` and handle the cases where dag_id does not exist
### How to reproduce
NA
### Operating System
NA
### Versions of Apache Airflow Providers
_No response_
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
_No response_
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [x] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
