shivaam commented on issue #63967: URL: https://github.com/apache/airflow/issues/63967#issuecomment-4107204415
I investigated this and believe this is **not a UI bug** — the behavior is expected. When you clear a DAG run, Airflow re-queues all tasks for execution. If the first few tasks are fast (completing in seconds), they finish **before the Grid view's next refresh cycle**, making it look like they were never cleared. **To verify:** Run a DAG where the first tasks have a long `sleep` (e.g., 60s), then clear. You'll see all tasks correctly transition to `None`/`queued` — confirming the clear worked. With fast tasks, steps 2-4 happen in under a second: 1. Clear → tasks reset to `None` 2. Scheduler re-queues immediately → `queued` 3. Worker executes → `success` 4. Grid refreshes → shows `success` (looks unchanged, but tasks were actually cleared and re-ran) I tested this on a live Airflow 3.2 instance with both fast and slow tasks — the Grid view correctly reflects task state in all cases. -- 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]
