SafeMahou5x
NNovu
•Created by SafeMahou5x on 8/26/2024 in #💬│support
We use github enterprise and again suddenly i'm unableUnable to login again with our github accounts
is also happening to a colleague , let me follow up in private
4 replies
NNovu
•Created by SafeMahou5x on 8/26/2024 in #💬│support
We use github enterprise and again suddenly i'm unableUnable to login again with our github accounts
eu
4 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
i messages u privately
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
sure that would be great
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
However the issue was reproduced using just the Novu console and test. So i guess that rules out any sdk issue.
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
Our use case is not driven by UI. We have built an event driven architecture where "events" happen and we process them via AWS Lambdas. The lambda is a Novu abstraction , using the novu sdk "@novu/node": "0.24.1"
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
It is, not only two .... we have a deadline and we were relying on having multiple digest steps ( to represent different user preferences ) and emit different emails based on that. Mantaining different workflow is not an option for us, because we have multiple notification types and we would end with 42 triggers to maintain. Only for a customer. And we plan to onboard more customers. So yes is a serious issue. We evaluated several candidates and novu won by the digest engine, the conditions , etc. If we cannot use that would be really hard for us to evolve our platform.
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
Digest
Condition: user.digestType == 4
Agregate only by suscriberId
When: Every day at 4pm
Email
Using template X
Digest
Condition: user.digestType == 8
Agregate only by suscriberId
When: Every day at 8pm
Email
Using template Y
We triggered 4 events aimed for users expecting agregation Every day at 4pm
We did this way before the time of the FIRST digest
{
digestType: "4"
data : "data01"
}
{
digestType: "4"
data : "data02"
}
{
digestType: "4"
data : "data03"
}
{
digestType: "4"
data : "data04"
}
We can see only FIRST digest is sent which is good.
However its contents are wrong
FIRST DIGEST : Number of events 7
4 - data01
4 - data02
4 - data02
4 - data03
4 - data03
4 - data04
4 - data04
So why 7 instead of 4?
why the events 2,3, and 4 are duplicated? And the first event is not?
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
This describes the test i made
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
You can see a wf named MAU-PLAYGROUND with the test scenario
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
Our environmentId 66432c55c4df36a964927b33
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
And before we started the official non free , i also explained our use case. That was one of the main reasons why thought Novu could be a good fit
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
In our business case is paramaount to be able to handle user preferences where they can set up monthly, weekly or four different daily schedules.
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
Hi thanks for your response. A couple of weeks ago I asked you for our business use case, and you suggested using multiple digest variants.
29 replies
NNovu
•Created by SafeMahou5x on 7/8/2024 in #💬│support
Unexpected duplication of events using multiple digests in the same trigger workflow
I can provide more details if required, you can see our workflow and how it looks in our corporative account
29 replies
NNovu
•Created by SafeMahou5x on 5/16/2024 in #💬│support
Unable to access "changes" menu. Cannot read properties of null (reading 'firstName')
Thanks! according to the docs, only suscriberId is mandatory ( we are doing some tests )
9 replies
NNovu
•Created by SafeMahou5x on 2/21/2024 in #💬│support
Handling complex "delivery time" user preferences
i read about the concept of variants. I thought that if I can attach to the suscriber metadata representing his/her daytime delivery preferences, I could create as many step variants as I want. For each variant use the schedule digest step just configured differently. So basically workflow level customization based on suscriber preferences. I think you are saying that
4 replies