"No Status" task filter leads to HTTP ERROR 422

[radumas]

Apache Airflow version

3.0.1

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

No response

What happened?

Have task instances with "No Status"

Click on "No Status" and receive Error 422. URL is airflow/task_instances?state=no_status&start_date=2025-05-29T14%3A54%3A16.740Z

Request receiving 422 is:

/airflow/api/v2/dags/~/dagRuns/~/taskInstances?start_date_gte=2025-05-29T14:54:16.740Z&state=no_status&limit=100&offset=0&order_by=-start_date

resp: Invalid value for state. Valid values are removed, scheduled, queued, running, success, restarting, failed, up_for_retry, up_for_reschedule, upstream_failed, skipped, deferred

What you think should happen instead?

Should return task instances that have no state.

How to reproduce

Haven't tested on a clean install, but I think sending this request on any install should produce the same result?

Operating System

Red Hat Enterprise Linux 8.10 (Ootpa)

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

Deployment details

I can post more if it feels relevant!

Anything else?

I think this happens all the time.

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

[karenbraganz]

I was able to reproduce this issue on my Airflow instance as well. I believe this is happening because the UI uses the "no_status" state instead of None , but this is not a valid TaskInstanceState, so it raises an exception here.

I can work on a fix for this.

[karenbraganz]

I added "no_status" to the tuple here.
return [None if s in ("no_status", "none", None) else TaskInstanceState(s) for s in states]

I am no longer seeing the Validation Error, but it is also not filtering any tasks with no status. Not sure why.