AN1RUDH
AN1RUDH
Explore posts from servers
NNovu
Created by AN1RUDH on 9/29/2024 in #💬│support
Novu is slow even after creating indexes
No description
19 replies
NNovu
Created by AN1RUDH on 9/4/2024 in #💬│support
Events keep getting merged with same old trigger event (Digest issue)
I've self-hosted novu (v0.24). It was working well previously. However, we've encountered an issue where trigger events are getting merged with a same (digest) event from past. (Please take a look at the video recording attached). I tried updating the digest schedule (can be seen in the video), but its still getting merged with the same exact (digest) event. I tried looking into logs (worker logs) but couldn't find anything useful. :/ Also, novu seems very slow (again, can be seen in the video). We've had M30-M40 tier mongo instance, yet we kept getting notifications form mongo for these --
Query Targeting: Scanned Objects / Returned has gone above 1000
Host has index suggestions
System: CPU (User) % has gone above 95
Query Targeting: Scanned Objects / Returned has gone above 1000
Host has index suggestions
System: CPU (User) % has gone above 95
The DB name created by default was test (not sure if this is expected). Lmk if I should post this in #⚓│community-self-host -- posted here as this seems to be unrelated to self-hosting. Thank you for your time 🙏
9 replies
NNovu
Created by AN1RUDH on 6/18/2024 in #💬│support
Triggering a workflow using topics does not do anything
Hi everyone, We've self-hosted Novu and were able get it in a working state. We're able to send notifications. However, when we tried to create topics and send notifications to those topic(s), we get back a sucess response:
{
"data": {
"acknowledged": true,
"status": "processed",
"transactionId": "677555f6-0d9c-4ae0-b12f-6d3254a07146"
}
}
{
"data": {
"acknowledged": true,
"status": "processed",
"transactionId": "677555f6-0d9c-4ae0-b12f-6d3254a07146"
}
}
But this actually doesn't do anything, nothing shows up in activity feed, not notifications are sent. (We have subscribers in those topics). I also checked the database and I don't see any records with transaction ID that we get back from the response. (I think mainly jobs collection) Also, took a quick look at API and worker logs but wasn't able to find anything useful. The way we trigger this was using the node SDK: (Also tried making an API call directly but the results were same)
const res = await novu.trigger('worklow', {
to: [
{
type: "Topic",
topicKey: 'my-topic',
},
],
payload: {
key: "value"
},
});
const res = await novu.trigger('worklow', {
to: [
{
type: "Topic",
topicKey: 'my-topic',
},
],
payload: {
key: "value"
},
});
However, if we send notification (trigger workflow) for individual subscribers, it works:
const res = await novu.trigger('worklow', {
to: 'subscriber-id',
payload: {
key: "value"
},
});
const res = await novu.trigger('worklow', {
to: 'subscriber-id',
payload: {
key: "value"
},
});
This sends the notification as expected and entry shows up in activity feed too. Thanks for your time. 🙏
8 replies