Over that past week, we've seen the TA correctly ID the timestamps of events for most of a day and then another day it will chuck all the events is to a bin for midnight that day. Today we're seeing that it's choosing timestamps for 2017 and 2019!?
The following line in the default props.conf makes it seem like it's expecting a timestamp formatted like so dd/mm/yy hh:mm:ss
but, the data from our FMC contains only unix epoch time stamps.