Unable to send notifications in 0.21.0
Hello. We are currently using Novu self hosted on version 0.16.3 in production. I tried to upgrade to 0.21.0 but got an error while sending notification that "Subscriber does not have an active integration".
It works perfectly fine if I use 0.20.0 version. Did anything change in 0.21.0 that we should be making changes to make the notifications work?
10 Replies
@Engineering Can it be issue with
integrationIdentifier field?
Because earlier we allowed only single integration per provider.@BiswaViraj I didn't run the migrations yet but wondering how we can do this in production since our app is already in prod
It will be easier to clone a fresh repo locally and update the .env to point to the Prod DB to run the migrations
our database is behind a Vnet so we won't be able to run it from our local
I am very late to the game here. I have the same problem upgrading from 0.20.0 to 0.24.7. I have run all the migrations and still get the error.
I have run the migrations from code @origin/0.21.0 (git checkout v0.21.x) and then run the migrations (successfully). Attached are my migrations scripts.
Help!
@Pawan Jain can you help out here?
@todd
Could you please share the error you are getting?
The same as above: "Subscriber does not have an active integration".
I reckon that there is a particular migration that must be run under a particular version of the codebase!
Thanks
@Pawan Jain
I am on 0.20.0 (container image)
I checkout various git branches to run the code as I run each of the migrations (listed in the script)
I then upgrade to 0.24.7
The error occurs on sending the email.
If I then roll back to 0.20.0, the errors disappears and the email is sent
The error is understandable that a default/active integration (email) is required I presume on the subscriber. So hence a migration.
But, what baffles me is that a new subscriber does have this problem too. So, perhaps it is something else.
I haven't tried other images less than 0.24.7
Todd
Or, am I looking in the wrong place and it is the integration that needs some upgrade!
I have looked at the code in the
send-message-email.usecase.ts and can see the origin of the error is looking through various layers.
I presume my answer is somewhere in the apps/api/migarations/integration-scheme-update where there are 3 migrations and one spec.
Note: I have run these under v0.21.0 branch of the code
@Pawan Jain any thoughts?@todd
Give me some time. I will take a look on this and share the possible fix