rachanadutta opened a new issue, #60703:
URL: https://github.com/apache/airflow/issues/60703

   ### Apache Airflow version
   
   3.1.6
   
   ### If "Other Airflow 3 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When clearing a task instance from the UI, the clear action succeeds but the 
UI does not reflect the cleared state.
   
   Specifically:
   - The clear confirmation dialog correctly shows the affected task instances 
with state `No Status`.
   - The Task Instances list still shows the previous state (e.g. `Success` or 
`Failed`).
   - Opening the individual task instance page also continues to show the 
previous state.
   
   This occurs for both mapped and unmapped task instances.
   
   
   ### What you think should happen instead?
   
   After clearing a task instance, the UI should refresh and reflect the 
cleared state (e.g. `No Status` / neutral state) in the Task Instances list and 
the individual task instance page, so that users can clearly see that the clear 
action took effect.
   UI can also show a success message like it does for delete task instance.
   
   ### How to reproduce
   
   1. Start Airflow using `airflow standalone`.
   2. Open the Airflow UI.
   3. Enable the `example_bash_operator` DAG (for unmapped tasks) or 
`example_dynamic_task_mapping_with_no_taskflow_operator` (for mapped tasks).
   4. Trigger the DAG and let a task instance succeed or fail.
   5. Navigate to the Task Instances view.
   6. Click "Clear" on a task instance (or "Clear all mapped task instances").
   7. Observe the clear confirmation dialog showing affected tasks with `No 
Status`.
   8. Close the dialog and refresh the page.
   
   The task instance state in the UI remains unchanged (e.g. still `Success` or 
`Failed`).
   
   
   ### Operating System
   
   macOS
   
   ### Versions of Apache Airflow Providers
   
   _No response_
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   Airflow installed using `pip` with constraints and started via `airflow 
standalone`.
   No custom configuration or providers involved.
   
   
   ### Anything else?
   
   Context: While adding the missing UI button for “Clear all mapped task 
instances” (using existing backend support) and testing the flow, I noticed 
this behavior.
   
   ### 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