Description

Over the last couple weeks I've come across a rather tricky problem a few times. One DAG run gets "stuck" in the queued state, while subsequent DAG runs will be stuck running (screenshot below). One of these issues was caused by max_active_runs being met when a task instance from a previously run DAG was cleared, and one of the tasks had depends_on_past=True. This caused the DAG run to be stuck in queued in perpetuity until it was realized that the task that wasn't getting scheduled needed the failed task in the preceding DAG run to be re-run, which in turn causes the stuck running DAG runs to be stuck in running. which caused quite a bit of confusion and stress.

Ideally there would be a new status (or a refresh of the no_status status), but a much simpler solution to this problem might be simply surfacing the full task instance details in the grid view, or at least adding a task's dependencies to the task instance details in the grid view.

Use case/motivation

I don't have a solid understanding of what underlies the UI, but IMO it'd be best to surface the full task instance details view in the task instance details sub-view of the grid view.

If that's too technically challenging for now or if there are other issues (for example, performance issues), it'd suffice to at least include the task's dependencies in the task instance details sub-view of the grid view.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct