naltimari opened a new issue, #62360:
URL: https://github.com/apache/airflow/issues/62360
### Apache Airflow Provider(s)
microsoft-azure
### Versions of Apache Airflow Providers
12.10.1
### Apache Airflow version
2.11.0
### Operating System
Linux
### Deployment
Official Apache Airflow Helm Chart
### Deployment details
Using CeleryExecutor on Azure Kubernetes, with Redis as broker and
PostgreSQL as db backend.
### What happened
When using the AzureDataFactoryOperator in 'deferred' mode (also happens on
sensors), the trigger always spits out this error just after it finishes:
[2026-02-23, 12:56:19 CET] {triggerer_job_runner.py:631} INFO - Trigger
<dag_id>/scheduled__2026-01-23T11:50:00+00:00/<task_id>/-1/1 (ID 1759854)
fired: TriggerEvent<{'status': 'success', 'message': 'The pipeline run
d036000c-xxxxx-xxxx-xxxx-969e7970133b has Succeeded.', 'run_id':
'd036000c-xxxxx-xxxxx-xxxx-969e7970133b'}>
**[2026-02-23, 12:56:19 CET] {base_events.py:1833} ERROR - Unclosed client
session
client_session: <aiohttp.client.ClientSession object at 0x798415e2acc0>
[2026-02-23, 12:56:19 CET] {base_events.py:1833} ERROR - Unclosed connector
connections: ['deque([(<aiohttp.client_proto.ResponseHandler object at
0x798415a67bf0>, 1201256.160092484)])']
connector: <aiohttp.connector.TCPConnector object at 0x798416103e30>**
The error shows up in the 'post-task execution' log section.
### What you think should happen instead
Seems there is some sort of unclosed session there, possibly with resource
leaks.
### How to reproduce
In our environment, it consistently happens whenever these operators are
used in the 'deferred' mode:
- AzureDataFactoryRunPipelineOperator
- AzureDataFactoryPipelineRunStatusSensor
### 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]
