raghavan-arvind opened a new issue, #71502:
URL: https://github.com/apache/airflow/issues/71502

   ### Under which category would you file this issue?
   
   Providers
   
   ### Apache Airflow version
   
   3.3.0
   
   ### What happened and how to reproduce it?
   
   An `ExternalTaskSensor` which succeeded in the queued state became orphaned 
and failed.
   
   Event log:
   
   ```
   
   2026-08-12 06:00:03 | running
   2026-08-12 06:00:12 | deferred
   2026-08-12 06:00:15 | state mismatch |   | Executor 
LocalExecutor(parallelism=200) reported that the task instance <TaskInstance: 
DAG_ID.<TASK_ID>_sensor scheduled__2026-08-12T11:00:00+00:00 [queued] 
ti_id=019ff5a1-147c-7951-8a4d-a97483c61ce0> finished with state success, but 
the task instance's state attribute is queued. Learn more: 
https://airflow.apache.org/docs/apache-airflow/stable/troubleshooting.html#task-state-changed-externally
   2026-08-12 06:00:16 | failed
   
   
   
   
   
   
   ### What you think should happen instead?
   
   Task should go to the success state.
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Docker-Compose
   
   ### Apache Airflow Provider(s)
   
   _No response_
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Official Helm Chart version
   
   Not Applicable
   
   ### Kubernetes Version
   
   _No response_
   
   ### Helm Chart configuration
   
   _No response_
   
   ### Docker Image customizations
   
   _No response_
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] 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]

Reply via email to