# Tag Historian missed data filling

**URL:** <https://forum.inductiveautomation.com/t/tag-historian-missed-data-filling/26606>\
**Category:** Ignition\
**Created:** [July 17, 2019, 6:19am UTC](https://forum.inductiveautomation.com/t/tag-historian-missed-data-filling/26606 "2019-07-17T06:19:18Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![gurovskiy-a](https://avatars.discourse-cdn.com/v4/letter/g/eb8c5e/32.png) [@gurovskiy-a](https://forum.inductiveautomation.com/u/gurovskiy-a)\
**Post date:** [July 17, 2019, 6:19am UTC](https://forum.inductiveautomation.com/t/tag-historian-missed-data-filling/26606/1 "2019-07-17T06:19:18Z")

</div>

We need help in solving the following problem.

There is a kep server that polls data from the PLC using the DNP3 protocol and Igntition 7.9.12 .  
The main requirement from which dnp3 was used is the restoration of the trend after a break and the restoration of communication.  
I see that Kepware gives the data with the timestamp that I need (tag.lastchange), but at the same time, I cannot write this data to the database using standard Ignition tools.  
In one case, the data is written to the end of the trend with the server time stamp; in the other case, this data disappears (does not insert into the database).