Make database errors in the REST API more human readable

[tirkarthi]

Apache Airflow version

main (development)

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

No response

What happened?

While trying to create a dag with same logical date this results in unique constraint error but the UI seems to display the sql query through _UniqueConstraintErrorHandler implementation which is not user friendly. It should say that the dagrun with logical_date exists which is more helpful.

What you think should happen instead?

No response

How to reproduce

1. Run a dag with a logical_date in the UI.
2. Run the dag again with same logical_date.

Operating System

Ubuntu 20.04.3

Versions of Apache Airflow Providers

No response

Deployment

Virtualenv installation

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

[bbovenzi]

I would say this is more of an API bug since we are display what we get back from fastapi

[eladkal]

Is this preventing creation of dagrun? If so I am not sure this should be categorized as low priority

[tirkarthi]

No, this is just about the error message part which could be used friendly when the logical date selected for the dagrun already exists.

[AkhilaNenavath123]

Unable to reproduce the issue in Airflow version 3, as there's no option to precisely match milliseconds when manually setting the logical time for the second DAG run.
First dagrun:

Second dagrun:

Could you please specify the exact version that needs to be used?

[tirkarthi]

You can still edit the input instead of using the datetime picker and try to trigger the dagrun twice using time including milliseconds. This is about the error message from the backend which could be improved.

This is on Firefox 136.0 on Ubuntu 20.04