HTTP 500 Error when triggering DAG with invalid parameters

[missaarohi]

Apache Airflow version

main (development)

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

No response

What happened?

When attempting to trigger a DAG through the stable API with invalid parameters, the API returns an HTTP 500 Internal Server Error. The error message shows 'Uuups'. This happens due to missing validation for the parameters before triggering the DAG.

What you think should happen instead?

The API should return a 400 Bad Request with appropriate error details instead of a 500 error.

How to reproduce

1. Use the stable API to trigger a DAG.
2. Send invalid parameters (e.g., missing required fields or incorrect values).
3. Observe the returned HTTP 500 error.

Operating System

Ubuntu 20.04

Versions of Apache Airflow Providers

apache-airflow-providers-google==5.0.0

Deployment

Official Apache Airflow Helm Chart

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

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[potiuk]

Won't fix - we are rewriting the APIs in Airlfow 3 with FastAPI and Pydantic validation - so validation will be built in. There are no plans to enhance the behaviour and make any changes to the API framework used in Airflow 2.