This is a typical U.I. internal issue on GCP. More people had this issue and it was solved. You can use the upload button as a workaround, but in order to solve it you have 2 options. In case you are entitled to have support you can open a support ticket, stating your context. The other option, in case you are not entitled for support is creating a public issue tracker.
To investigate this issue further, the entitled teams will need you to record a HTTP Archive HAR while
recreating the steps that led to the error, then attach the saved HAR file to
the issue description. HAR files contain header and request information for a browsing
session and are useful for troubleshooting a variety of problems. Detailed
instructions can be found here.
A HAR file can contain sensitive information including, but not limited to,
passwords, cookies, private keys and credit card numbers. As such, it is better that you review the generated HAR file, and sanitize it of any such
information.
Additionally, it is advised that you sign out of any sessions that were active
during the time that the HAR file was generated in order to invalidate them.
Incognito mode is not enough to guarantee this, as the session may still be
active, even after closing the incognito window.