Vercel errors when I open the Preview in Novu using Novu Echo
I'm using Novu Echo and I have a couple of steps configured
In App -> Digest -> Email
When I go to Novu Workflows and open the one created by Echo, I get a bunch of errors reported in Vercel.
Is this normal? How can I fix it or ignore if it's expected?
6 Replies
Hi @BrunoLM, I'm an AI assistant for Novu. While a team member reviews this question, I'll see if I can find relevant sources for your question.
@BrunoLM, you just advanced to level 2!
-----------------------------
While I generate an answer, here are some sources that might be helpful:
* Others
* Workflows
* Messages
* Dev Studio
-----------------------------
Answer
It sounds like you are experiencing technical difficulties when integrating Novu Echo with Vercel. This could be related to a variety of factors, such as configuration issues or network-related errors.
Given the symptoms you described, it's possible that there could be a CORS or networking issue when attempting to sync or execute workflows that integrate with external services like Vercel. However, to provide a precise solution, I would need specific error messages or more details about the errors you are encountering.
If the errors appear to be related to CORS, keep in mind that Novu APIs are designed to be used on the server side. Using the API from the browser side might cause CORS errors (1) . Ensure you are making API calls from server-side environments, or utilize Novu's client libraries appropriately.
For more comprehensive troubleshooting:
1. Check the network requests and responses in your browser's developer tools to identify any potential CORS or networking issues.
2. Verify that your Novu and Vercel configurations are set up correctly, paying close attention to any required credentials and permissions settings.
3. Review any recent changes to workflows or integrations that might have affected the setup.
If none of these steps resolve the issue, it might be beneficial to look into the specific error logs provided by Vercel and Novu for more detailed diagnostics.
For deeper integration issues or persistent problems, consider revisiting the Novu documentation or checking with the Novu community for insights and common solutions related to Vercel integration.
For more information, you can refer to the Novu documentation on managing CORS errors and using APIs server-side.
: Others
Got it. Tagging @Support for additional help.
Hi Bruno, thanks for reaching out.
The error messages you are seeing are a result of failed requests (BadRequestError) to preview your step - it's most likely occurring when you are in Echo Studio and previewing the steps, without having all the payload or inputs provided.
Unfortunately today we don't provide the ability to opt-out of error messages when consuming the Echo Client. We have it on our July roadmap to take a deeper look at customizing the errors/logging capability, we'll add this feedback to our ticket.
We'll share an update widely when we implement better customization for the Echo client logging capability.