Internal Server Error when searching with partial dates in Find a Record

[dikwickley]

Description

Sometimes when partially entering the date in the Record Search Field, it randomly throws internal server errors.
Sometimes it throws the intended InvalidDateFormatAPIException but other times it UnboundLocalError.

Here is a recording of the behaviour:

Screen.Recording.2023-12-03.at.1.33.13.PM.mov

Also, it would be good UI/UX to show the user the date is invalid. In case when the user has just put an incorrect date time format and the server returns a 400 BAD REQUEST InvalidDateFormatAPIException. The user won't know as the table still shows the loading state.

Expected behavior

• Server should not throw 500 internal server error and always throw InvalidDateFormatAPIException in case of wrong date format.
• User should be conveyed if their input date is incorrect.

To Reproduce

Environment

• OS: macOS
• Browser: Chrome
• Other info:

Additional context

[seancolsen]

Thanks for reporting this, @dikwickley. Your video is very helpful.

Server should not throw 500 internal server error

Agreed. The scope of this ticket should be constrained to this API problem.

You've also described some UX problems. Those should be covered by #2327, which I imagine you might be interested in working on.