Hi,
We are getting a lot of data stuck in Store & Forward with a 'duplicate entry for primary key'. For example here is an example data entry:
Looking at one of the points:
value path="Fields/Slade Park/Is Connected" datatype="0" mode="0" timesource="1" timestamp="2024-01-28 22:28:58.927" quality="192">true
Millisecond timestamp = 1706441338927
Tagid = 32309: found from query:
If I query the historic table (for jan) the last entry we got has the timestamp: 1706440570890 ( 2024-01-28 22:16:11.890 AEDT)
If I search the table for that t_stamp it wont return any values:
So I'm not sure why the data isn't being recorded when there doesnt seem to be any entries with that timestamp (or tagid).
This has caused a major problem as trends now show the value has still 0 (because the state hasn't changed since).
Maybe I'm missing something about the storing/conversion of timestamps ?
Is there another reason the value isn't being added ? Or does every value in the dataset need to be unique for all data to be inserted ?
Thanks,
Ben