Dashboard and headless stopped loading
I just noticed I can not see my data in Novu cloud and novu is not loading on my website.
Any known issues on your side?
20 Replies
@kingen ✌🏻
Can you please logout and login again?
yes I did that, still same issue 🤔
Hi @kingen ✌🏻 could you please open the console in the subscriber page and see if there are any errors there?
Console is working again. Reason for me checking out the console is that https://docs.novu.co/api-reference/subscribers/update-subscriber-global-preference have stopped working for me. Was there any change to it?
For example I have this request trying to set the email channel preference that has stopped working. I get a 200 response but the response only has the
in_app channel 🤔
ah, I'm using
@novu/headless , I'll try to replace it with @novu/js which seems to be the new way?
okey I tried @novu/js, doesn't work for me because I'm on the old workflows... Would be helpful to mention that on https://docs.novu.co/inbox/headless/get-started
somehow my suspicion is that https://v0.x-docs.novu.co/notification-center/client/headless/api-reference#fetchuserpreferences was changed. Any recommendation on how to debug this? 🤔@kingen ✌🏻 checking this with the team right now 🙏
Any update? 🙏🏻
@kingen ✌🏻
Could you please check again? We fixed one bug in subscriber preference flow
same thing, I'm missing the email channel 🤔
@kingen ✌🏻, you just advanced to level 3!
Hi @kingen ✌🏻 , we identified an edge case where using the Subscriber Preference API with new Workflows resulted in the preference resolution not respecting Subscriber Preferences. The fix was deployed yesterday.
Please try again and let us know if you see any further issues 🙏
Regarding the Subscriber Preference response, we now only return channels in that payload based on the Workflow step channels available to the subscriber, this is why you don't see
email. For example, if you only have Workflows with the in-app channel used, you would only see in_app in the response. You can still send other channels in the request, they just won't be returned in the response. This change ensures that Subscribers only see channels that are relevant to them.Ah, thanks for the response 🙏🏻
So just to be clear, there was a breaking change and I must adjust my code now? I have been using the global subscriber preference API to store email preference even though I'm currently only using Novu for
So just to be clear, there was a breaking change and I must adjust my code now? I have been using the global subscriber preference API to store email preference even though I'm currently only using Novu for
in_app in my workflows. A problem for me is that this state is now lost for all my users => I have no idea who wants emails or not...Hey @kingen ✌🏻 , you are right, this was indeed a breaking change, we didn't anticipate external Subscriber Preference consumption for use-cases such as yours. We are reverting the behaviour so that Subscriber Preference endpoints return both active + inactive channels by default, with the addition of an
includeInactiveChannels query param that will enable API clients to control the behaviour. The query param is true by default, returning the endpoint behaviour to the previous state.
Our apologies for this disruption! You can expect the change to be deployed into Novu Cloud by tomorrow at the latest. You're welcome to follow the progress of the PR here.GitHub
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.
Thanks for the update! 🙏🏻
Hey @kingen ✌🏻 , the change is deployed. Let us know if you have any further questions or support needs!
@Richard Fontein do I need to update something on my side?
@novu/headless is still making request seen in screenshots without the email key returned. I updated @novu/headless to 2.0.3.
Hey @kingen ✌🏻 , at present only the
GET /v1/subscribers/* Preference endpoints support provision of the includeInactiveChannels flag to return preference channels that do not belong to active workflow channels. The /v1/widgets and /v1/inbox APIs return only active preference channels. Please note that the latter APIs are not considered public at this time per the API Reference docs and therefore fall outside of the breaking change remit discussed above. We would be open to pull requests to add this capability to the Widget & Inbox APIs, alongside a related change to the <NotificationCenter /> + <Inbox /> components - a similar approach as taken for the Subscriber controller here can be taken. If you would like to contribute, we can provide guidance for the Widget+Inbox changes.
Would you be open to sharing more information on your use-case to send email outside of Novu? More context will help us to prioritize this issue on our backlog and uncover the full story behind consuming Novu without the delivery mechanism so we can best support related use-cases in the future.@kingen ✌🏻
Following up on this
hey sorry for being slow!
My use case is transitory...
Decided on novu and added some simple workflows for just in_app notifications in our web app.
We then decided to add email to the notifications (just before you were about to release
@novu/framework and workflows in code), therefore we decided to add the email sending outside of current workflows until we migrated to the new workflows.
Now we have not yet migrated to the new workflows, because of priorities...
And I don't really see us prioritising this now unfortunately.Thanks @kingen ✌🏻