Blocking APIs for me?
We have sent the first batch of users notifications which was successful. Now we are trying to use topics which work perfectly on my local machine but when I try to test it on staging or development servers I am not getting any notification, are there any restrictions that are there for the Novu APIs?
13 Replies
Hi @ManwinderSingh, 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:
* NodeJS quickstart
* .NET
* Java quickstart
* Go quickstart
-----------------------------
Answer
There are no specific restrictions mentioned for Novu APIs that would block notifications on staging or development servers as long as the configuration is correct. However, there are a few things you could check:
1. API Key and Configuration: Ensure that the API key and configuration settings are correct and consistent across your staging or development environment.
2. Network Issues: Verify that there are no network issues or firewalls blocking the requests from your staging or development servers.
3. Logs and Errors: Check the logs and any error messages that are returned from the API calls. This might give clues about what could be going wrong.
4. Rate Limits: While not explicitly mentioned in the official docs, rate-limiting could be an issue if you're sending a lot of notifications in a short period (especially relevant for providers). Refer to the discussion on rate-limiting for more context (1) .
5. Caching Issues: If you're self-hosting or using a caching layer, ensure that the caches are being invalidated properly when changes are made (2) .
For specific implementation details on using topics, you can refer to the respective language quickstart guides:
- NodeJS quickstart (3)
- .NET quickstart (4)
- Java quickstart (5)
- Go quickstart (6)
- Ruby quickstart [(7)](https:
//docs.novu.co/quickstarts/ruby#topics)
Got it. Tagging @Support for additional help.
@Pawan Jain Need help here
@ManwinderSingh
Could you please share more details for this
staging or development servers
We have two environments development and productionFor development server I used the development keys
For staging server I used the production keys
Development server is development environment
Staging is production environmenr
@Pawan Jain please check this on priority
@ManwinderSingh
If possible please share the environmentId in which you are facing issue
and transactionId of the event
Better if we can get on a call and resolve this issue ?
{:data=>{:acknowledged=>true, :status=>"processed", :transactionId=>"d13b044a-0bdd-4362-8c96-ba30fa4f5902"}}, transaction_id: d13b044a-0bdd-4362-8c96-ba30fa4f5902
topic: manwinder, subs:[332649], message: {:success=>true, :message=>"Successfully triggered notification for topic manwinder, details: {:name=>"nonhlpsmalluserslessthan10listings", :topic_key=>"manwinder", :subscribers=>[332649], :expire_at=>2024-05-16 18:31:11 +0000, :payload=>{:title=>"Migrate to our new pricing algorithm - Hyper Local Pulse.", :body=>"Click here to know more.", :notification_type=>"nonhlpsmalluserslessthan10listings"}}"}
Please check this
I didn't get any notificaiton for this one
@Pawan Jain Can you help here?
@Pawan Jain Can we please get your assistance here? any chelleges you guys are facing?
Hi @ManwinderSingh coult you try please addin
IS_TOPIC_NOTIFICATION_ENABLED=true when running both API and Worker servers? Just to double check that@Dima Grossman Where specifically? in bnody or the query params?
When starting your docker images
Why isn't this covered in the docs @Dima Grossman ?
@Dauntless I believe this was missed, this feature flag will removed in the upcoming version. So no need will be to specify it