I have a quick follow up to this one --
We have configured editor tracking to store dates in our local time zone (mountain) so as to not cause confusion when users see the raw data. The feature service that's being polled is also configured for dates in MTN time.
Looking at the debugger messages, it seems that the cache time is being converted to UTC (7 hours ahead) -- so any new data that comes in during the next 7 hours window is missed --
I'm wondering if there's a way to reinforce the time zone through GeoEvent -- either through the input connector to cache the local time or to convert the time in the new records to UTC before evaluating the filter?