You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem: I would like to know why tasks are not being scheduled when I expect them to be.
When debugging it would be nice to expose task dependency states, this can be especially crucial in production systems.
I would like to quickly be able to see why a task (or dag run) is in its current state, specifically the queued -> running or blank -> queued states. This would be most useful to me in scheduler logs and/or in the UI.
Common examples might be task dependencies not completed, pool slots full, max active dag runs exceeded, execution date not yet reached.
The text was updated successfully, but these errors were encountered:
Dear Airflow Maintainers, cc: @mistercrunch @r39132,
Problem: I would like to know why tasks are not being scheduled when I expect them to be.
When debugging it would be nice to expose task dependency states, this can be especially crucial in production systems.
I would like to quickly be able to see why a task (or dag run) is in its current state, specifically the queued -> running or blank -> queued states. This would be most useful to me in scheduler logs and/or in the UI.
Common examples might be task dependencies not completed, pool slots full, max active dag runs exceeded, execution date not yet reached.
The text was updated successfully, but these errors were encountered: