Ah, good catch! This should be fixed and show a proper error message.
I also found another path, via bulk actions:
