It looks like you have a program, in this case a shell script, and not a program launcher. To be exact, that is the dialog you get when opening a text file with the x (execute) permission set.
OK, the formatting now makes it possible to see the correct details.
I’ll guess the file has no “x” (execute) permission. It can be set in the file properties.
It has other issues because the password is piped so interacting with it won’t work and may get stuck. The launcher can be set to “Application in Terminal” to actually see the result.
My guess is the “sudo” element of the commands. Sudo normally requires that you enter your password. But, by having this built into a launcher and so not offering a terminal in which you can enter your password, when prompted, means it will hang at that point and never fully execute.
I have one method to get round this issue, if you want to know it.