My though exactly. Here's some additional info:
The query the generated the even above runs every day at 23:47. I created a similar query (same structure but different data) and set it to run at 23:37. It shows a similar issue, although instead of one event with the wrong time, it generates two. All three of the following events show a timestamp of "12/1/14
11:30:00.000 PM":
12/01/2014 23:50:00 -0500, search_name="ABC volume", search_now=1417322220.000, info_min_time=1413689820.000, info_max_time=1417322220.000, info_search_time=1417322223.036, high="40.08991", low="0.42437", pred="20.257143"
12/01/2014 23:40:00 -0500, search_name="ABC volume", search_now=1417322220.000, info_min_time=1413689820.000, info_max_time=1417322220.000, info_search_time=1417322223.036, high="39.87579", low="1.72421", pred="20.800000"
12/01/2014 23:30:00 -0500, search_name="ABC volume", search_now=1417322220.000, info_min_time=1413689820.000, info_max_time=1417322220.000, info_search_time=1417322223.036, high="42.55996", low="2.64004", pred="22.600000"
As before, timestartpos and timeendpos are 0 and 25 for all events. Trying to whittle this down to a minimal test case, but it's looking like there's some dependency on search time.
... View more