As mentioned in previous comments, such error is not expected to happen, especially not for devices, that are already "enrolled" with ESET Push Notification Service (happens automatically after ESET Management Agent is deployed and has network connectivity to the service).
Regarding cool-down, there is indeed a limit (around 1 minute), but there is no indication to the user -> device will just not trigger connection to PROTECT more often, i.e. if there are multiple attempts to wake-up device in short period of time, they will be grouped and operation will be delayed.
