Thank you for specifying this.
Indeed, there is a validation about this on the server but it does not cover the current number of devices (because it cannot validate how much devices you are going to have in the future).
At the current stage, the validation will cut down requests with UseLocalTime
set to true
that try to schedule a notification which NotificationDate
is in the past according to UTC time. This means that if your time zone is -5 hours UTC time, you cannot schedule a notification with a notification date in the next 5 hours ahead of the current time in your time zone. Can you confirm that this is the behavior you encountered?
I do agree that there are some missing explanations in the docs on this matter which we will address.
Meanwhile, let me know if you have further questions or suggestions.