This sounds like a regression on Databricks UI side.

This is part of a project in which we need non-technical users to be able to perform the procedure strictly through the Databricks web UI.

Anyways, I contacted Databricks support, let's hope they fix it.