#3505 [Core feature] improve pyflyte usage error for missing projects Issue created by cosmicBboy Motivation: Why do you think this is important? When I do

pyflyte run --remote -p nonexistent_project ...

the error message that's produced contains a whole lot of information about the task while not reporting what is actually wrong, which is that

nonexistent_project

doesn't exist in the remote Flyte cluster. See here for full context on what the current error message is. Goal: What should the final outcome look like, ideally? Consider specifying an invalid project or domain as simple input errors and should fail quickly with explicit messaging i.e. "Project 'flytesnacks' not found". A full stack trace is hard to mentally parse for such a simple input error even if it did actually say why it failed in the message. Describe alternatives you've considered NA Propose: Link/Inline OR Additional context No response Are you sure this issue hasn't been raised already? ☑︎ Yes Have you read the Code of Conduct? ☑︎ Yes flyteorg/flyte