Replies: 2 comments
-
I have a similar concern. For instance, when an incorrect OpenAI Secret Key is provided, an error like "AuthenticationError: 401 Incorrect API key provided..." appears in the terminal. However, I'm unable to capture these errors using a try-catch block with the RSC/Generative UI approach. @twxxk, do you have any updates or solutions for this? |
Beta Was this translation helpful? Give feedback.
-
Just to bump, I've got a similar problem where if a tool is called within |
Beta Was this translation helpful? Give feedback.
-
I am using render() to get the LLM response. I would like to catch and handle errors from LLM models like 429 and 500.
https://sdk.vercel.ai/docs/api-reference/generative-ui/render
Currently the error generates the stack trace on the server and the client does not generate anything which is a very bad experience..
I wrote try...catch around render but it did not work.
How can I catch the error and generate a user-friendly message?
Beta Was this translation helpful? Give feedback.
All reactions