-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Negative numbers in failed notifications #102
Comments
Hi @matteomorreale yes, it looks a bit weird. Could you please check if some notifications failed totally in any of those dates that have negative numbers? Thank you! |
I cannot find negative numbers elsewhere, but maybe it's related to the old subscribers with OneSignal? |
No, not negative numbers. I want to confirm if maybe some of the notification jobs you sent in August 25 failed, and how many in total for that day. This will help us in understanding what the issue was, thank you! |
Almost 200 notifications failed for every push sent in August 25, with 9 pushs in total |
We will change the way in which we count the failed notifications. This will probably impact the reports but will be more reliable. Adding it to the backlog. |
This will be released in |
This has been included in |
Hi, the graph with the notifications recap has an issue related to failed notifications.
As you can see here
https://www.awesomescreenshot.com/image/12722763?key=aad4e489f1c578578798153d370a74b5
the few days old failed notifications are in a negative number and I really don't know why.
The text was updated successfully, but these errors were encountered: