Webtrends did not see the data hit their servers during the time period that you were missing the data from. They report that if the device is unable to make a connection, it will queue up events to a certain point. When that limit is reached, it starts to remove older entries. Also, it limits how many times it tries to send data. Webtrends suspects that network coverage is likely the cause of this.
The settings are in the config.xml:
wt_dc_event_table_size_maximum is the maximum table size and defaults to 10000. If this fills up, we will trim off older events, not stop collecting new data. I believe we also remove the 10 oldest events so as not have to call the trimming process for every event once it's hit 10000.
wt_dc_event_retry_maximum is the max number of times to try sending the data and defaults to 5. I've been advised that after 3 tries, we do have the SDK wait and try again at a later point.
Tim Windsor
Application Development Consultant
