Skip to content

"No Status" task filter leads to HTTP ERROR 422 #51246

Closed
@radumas

Description

@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"

Image

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

Image

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

Metadata

Metadata

Assignees

Labels

area:APIAirflow's REST/HTTP APIarea:UIRelated to UI/UX. For Frontend Developers.kind:bugThis is a clearly a bugpriority:mediumBug that should be fixed before next release but would not block a release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions