airflowctl: List dagruns without dag-id

[amit-mittal]

Apache Airflow version

3.1.7

If "Other Airflow 3 version" selected, which one?

No response

What happened?

$ airflowctl dagrun list '--state=queued' '--limit=5'
2026-02-05 21:52:17 [warning  ] Server error                   [airflowctl.api.client] extra={'detail': 'The Dag with ID: `none` was not found'}
Server response error: Client error message: {'detail': 'The Dag with ID: `none` was not found'}
Client error,  Please check the command and its parameters. If you need help, run the command with --help.

The above command fails.

What you think should happen instead?

All the flags of dagrun should be optional and if dag-id is not specified, it should find the dag-runs across all the DAGs.

How to reproduce

apache-airflow-ctl==0.1.1

Operating System

Darwin

Versions of Apache Airflow Providers

No response

Deployment

Other

Deployment details

No response

Anything else?

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

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

[abhijeets25012-tech]

i would like to contribute

[shahar1]

i would like to contribute

@abhijeets25012-tech Please note that you're already assigned on 3 other issues, and I notice that you ask to be assigned very often in new issues.
While there is no technical problem with that at the moment, and I appreciate your will to contribute - I'm concerned that in the current situation:

1. It will take too long for you to actually resolve the issues you're currently assigned for.
2. It will prevent opportunities from other new contributors.

I'd like to suggest focusing on the assigned tasks first, before asking to be assigned in future issues.
Specifically for this issue, as @henry3260 created has already created a PR - I'd like to let him finish it.
Thank you for your understanding!

[abhijeets25012-tech]

ok thanks ,that will be fine

[k-nithin]

I would like to work on this issue.

[vinitsingare]

Currently, airflowctl dagrun list allows running without dag-id but the REST API requires it, resulting in an error.
The expected behavior is to list dagruns across all DAGs when dag-id is not provided, similar to the Airflow UI right?