Steps to reproduce:
Highloaded proxy (or proxy should be unavailable for "perceptible" period of time)
Nodata triggers (default ones, without strict parameters)
While proxy is unavailable all triggers are suppresed as they should be.
But when proxy comes up (lastseen is near 'now') it start to send collected data from the olde ones
Server process nodata trigger. Is proxy available -> yes. Is there data for (let it be) 10 min -> No, just 30 minutes old data come to the server

So problems was suppressed while proxy was unavailable, but when proxy becomes available nodata trigger fire because of proxy queue

As possible option we can set (probably configurable) period to suppress problems after proxy is available to process all queue from it. Probably there are better options

Regards, Elina