--
NNovu
•Created by jarredwitt on 9/5/2023 in #💬│support
Error: Missing lock for job
I haven't been able to find it in GitHub issues, so I am afraid @jarredwitt didn't have time for that.
29 replies
NNovu
•Created by PidginEnemy on 11/7/2023 in #💬│support
Error in topics endpoint
We are not sure about what would the sweet post but would you mind to help us testing this 2 limits?
- A topic with 100,000 subscribers
- A different topic with 500,000 subscribers
That would help us a lot to decide how to tackle this. Sorry for using you as guinea pig. 🙏
10 replies
NNovu
•Created by PidginEnemy on 11/7/2023 in #💬│support
Error in topics endpoint
Hi @Евгений Толченников , thanks for sharing this with us. Right now we are not limiting the amount of subscribers a topic has so you have hit an infrastructure limitation. When we implemented the Topics API we already had in our minds this situation would happen but we didn't have any metric that could allow us to think how to handle topic subscribers limit.
We appreciate your feedback as it will help us to tackle that issue. So right now we are sorry but you will have to manage your subscribers in batches in different topics to overcome this limitation. 🙏
10 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Sorry, I wasn't aware of that issue open.
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
I was just doing that 😄
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Please open a GitHub issue with all this information if you haven't done it yet so we can prioritise the investigation. Thank you very much for being patient and providing so much info. 🙏
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
That's true and that's why I asked about changes. It is weird. To just clarify, are you able to enable APNs in your Dev environment?
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Just last question before asking you to open an issue because indeed it looks we are into something. Confirm me that the menu entry Changes doesn't have any changes to promote from Dev to Production and we are dealing with the same configuration.
Anyway in the Development environment you should already be able to send notifications to both FCM and APNs when both are active.
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Yes, can you double check in your development environment that botch FCM and APNs providers are set as active both? We can just double check the behaviour in your DEV environment.
After that I would ask you to double check that you have set the device tokens appropriately for the subscribers, the ones meant to be notified through FCM in that integration and the ones meant to be notified through APNs in that other integration.
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Here you have a small reference regarding setting the feature flags in case you need it: https://docs.novu.co/community/run-in-local-machine#set-up-your-environment-variables
56 replies
NNovu
•Created by serafeimo on 3/22/2023 in #💬│support
Issue while having both FCM and APNS active
Can you try setting in the environment variables of the API, Worker and Web apps the following environment variable:
This will enable the multi provider feature that includes the fix of the bug you have noticed and the fix that has been applied in that PR.
Notice that this feature changes the behaviour for email and SMS providers allowing to have multiple active providers set. So try this in a DEV environment to see that it shows the fix but without affecting to your current flow, as a caution. measure.
56 replies
NNovu
•Created by serafeimo on 9/27/2023 in #💬│support
ReplyError: CROSSSLOT Keys in request don't hash to the same slot
Also can you confirm you are talking about v.0.19.0.
9 replies
NNovu
•Created by serafeimo on 9/27/2023 in #💬│support
ReplyError: CROSSSLOT Keys in request don't hash to the same slot
Hello. Yes, the cluster mode is tested and working right now in our Cloud environments.
I am having a suspicion considered our code and our setup.
May I guess that you are using Elasticache for both the Redis Cache service and for the Redis Cluster service? Either 2 different instances or the same for both.
Can you confirm my guess?
9 replies
NNovu
•Created by Pawan Jain on 9/9/2023 in #💬│support
Create topic inline with trigger similar to subscribers
This would introduce a bigger complexity to handle as we allow to trigger an event with mixed recipients. For example to different topics and different subscribers not related to those topics in the same trigger request. There could happen extreme complex cases where you would try to send a trigger to a topic not created with subscribers not still in the database. A lot of checks to do causing more computation time and increasing the average response time of the endpoint.
9 replies
NNovu
•Created by Pawan Jain on 9/9/2023 in #💬│support
Create topic inline with trigger similar to subscribers
We considered that is overloading the workflow trigger with an extra job that is not its responsibility and the trigger already handles a lot of complex logic. At any time in any use case a call to either validate that a topic has subscribers assigned needs to happen. Either before triggering the event or during the runtime of triggering the event.
We considered it was better to have users to do their checks before triggering an event and let them decide what to do, if trigger the event for a topic or not.
9 replies
NNovu
•Created by jarredwitt on 9/5/2023 in #💬│support
Error: Missing lock for job
This might be the most important part, so please specify it in the issue so any of us who could pick it up knows exactly how to test it and what to look for.
Really appreciate the clarity on explanation what you are doing. It will be very helpful for us. Thank you.
29 replies
NNovu
•Created by jarredwitt on 9/5/2023 in #💬│support
Error: Missing lock for job
Sorry for not being clear.
In the screen you are sharing we send an error report to the user that the subscriber that should receive this notification has not configured properly the Push channel. Now, there could be 2 options: that for any reason you haven't configured the channel provider for Push properly or that, as you said, the subscriber has opted out from receiving push notifications.
Being the second case wouldn't make sense us to run the jobs of the notification related to the push notification as we are not meant to send them, therefore not incurring in any job running side effect (like locking the job for scheduled notifications features and many more). So that's something we should also review if we are throwing any unexpected error or we are not managing the flow properly or if for internal reasons it needs to behave like this. If it is a bug, we will need to fix it in a future release. If we understand it is not and it is our chosen behaviour we might think in ways to not pollute that much the logs, though that could be a double edge sword in certain cases.
Hope this makes more sense.
29 replies
NNovu
•Created by jarredwitt on 9/5/2023 in #💬│support
Error: Missing lock for job
I think is worth you to open an issue in GitHub. I think the lock error is misleading in a way and the problem could come elsewhere. Wouldn't make sense for us to execute part of the workflow if the channel is not configured by user preferences (opt-out).
I'd ask you to provide the current version you are using where this happens, the example workflow and the configuration of the different steps and clarify as you did right now how you have your infra configured reminding us that you have set Redis Cache Services with the values of REDIS_HOST and REDIS_PORT. 🙏
Thus we can investigate what issue might be on our side if we missed something or if it something expected and we might need to handle the logging differently to not pollute your logs.
29 replies
NNovu
•Created by jarredwitt on 9/5/2023 in #💬│support
Error: Missing lock for job
Since which version did you experience this?
29 replies