#3404 [Core feature] Improved flytekit error messages Issue created by cosmicBboy Motivation: Why do you think this is important? Today, error messages are hard to decipher: all the user knows is that something went wrong in a task/workflow. The purpose of this issue is to improve these error messages by: • providing richer context on where the error occurred exactly • if applicable, provide a hint about how to address the error 🤝 Community call to action! If you'd like to contribute to this effort, please create a comment on this issue with the following information: 1. A minimally reproducible code snippet that produces the error 2. The current error text with full stack trace 3. Ideas on how to improve the error message Goal: What should the final outcome look like, ideally? First we need to compile a list of errors to improve! Describe alternatives you've considered The alternative is the current state, which makes the UX suffer 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