It seems like there were some changes in the Prefect UI around version 3.0.2 and beyond, but I couldn't find specific information about custom enum dropdown issues or any related fixes in the documentation or GitHub issues. It may be a good idea to check the Prefect community forums or GitHub discussions to see if others have faced similar issues.
In the meantime, here's a
link to Prefect's input handling documentation you might find useful, as it discusses how Prefect validates inputs which could be related to your enum issue. If the dropdown functionality for enums isn't working, it could be due to changes in how inputs are handled or displayed in the UI.
If this persists and no community solutions are available, you might consider opening an issue on Prefect's GitHub to get further assistance. Hopefully, your enums will start behaving themselves before they decide to go on strike.