Message content could not be generated
I use SendGrid for emails and in-app notifications. I have several workflows, but sometimes when I send notifications, I encounter an error: "Message content could not be generated." When I check the details, I find that the "error" field is empty. When I try triggering the email again using a curl request, I see that the email is sent successfully. This error occurs intermittently, at different times of the day and with different emails. I wrote to the chat but i am left with a seen for many times. Also i issued a bug in github but still nothing.
8 Replies
Hi @Safi, 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.
-----------------------------
While I generate an answer, here are some sources that might be helpful:
* Email
* How to use Novu to send notifications to a channel in a Discord server
* Messages
* Workflow Editor
-----------------------------
Answer
The error message "Message content could not be generated" you've encountered can arise from improperly formatted HTML content within your notifications when using SendGrid for emails through Novu. This is especially true if the HTML content is not properly formed or contains syntax errors (1) . While the specific scenario you're experiencing, particularly the intermittent nature and the empty "error" field, isn't directly addressed in the provided sources, ensuring your HTML content is correctly formatted is a good first step to troubleshoot this issue.
Given the intermittent success of your notifications when retriggered via a curl request, it might also be beneficial to review the specifics of each workflow and notification content for any subtle differences that could be contributing to this issue. Additionally, inspecting any recent changes in your workflows or the content structure that coincide with the onset of this issue might offer clues.
Since you've already reached out through chat and GitHub without resolution, and considering the information provided doesn't directly cover your exact situation, I recommend closely reviewing any related documentation or community forums for any updates or similar cases. If the problem persists, continuing to engage with the community or monitoring GitHub for any updates on your reported issue might yield further insights.
when i trigger it via a curl request, it is sent with success. So i think it is a bug that happens several times a week.
Got it. Tagging @Support for additional help.
@Safi Thanks for creating a support post and apologize for the delay in response.
I have shared the above issue with team. Since this issue is occuring rarely and only within your environment, it is making a bit hard to debug and fix this issue.
Could you please invite
[email protected] to your organization so that we can debug it from our endyou are invited,admin is [email protected]. I sent some not transaction ids in the chat. Happens regularly.
i wrote several times. It keeps happening. Last one is with transaction id : 066bb2e4-5e74-4c18-a2f1-199c653dfd5f
@Safi, you just advanced to level 1!
when i call the same request via curl, it works. Happens with different workflows.
@Pawan Jain