# History : Max Time Beetween records not applied

**URL:** <https://forum.inductiveautomation.com/t/history-max-time-beetween-records-not-applied/10621>\
**Category:** Ignition\
**Created:** [October 14, 2015, 12:30pm UTC](https://forum.inductiveautomation.com/t/history-max-time-beetween-records-not-applied/10621 "2015-10-14T12:30:56Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [October 14, 2015, 12:30pm UTC](https://forum.inductiveautomation.com/t/history-max-time-beetween-records-not-applied/10621/1 "2015-10-14T12:30:56Z")

</div>

We try to log some sqltag in history with 1 data point per seconds for some period.  
For that purpose we override some history’s parameters of the sqltag (with system.tag.edit)

We obtain in history database, 1 point per 2 seconds instead of 1 point per 1 seconds as expected.  
 ![:scratch:](https://us1.discourse-cdn.com/inductiveautomation/original/1X/76d1620bec252bfac07050c889ff5a91dc8a9c25.gif ":scratch:")  
See File attached for the detail: [history\_1second.pdf](https://us1.discourse-cdn.com/inductiveautomation/original/2X/5/52c378438bab862767106f306b97ddd9fc6f2a0d.pdf) (666 KB)

---

<div class="post-metadata">

**Author:** ![Pat](https://avatars.discourse-cdn.com/v4/letter/p/8491ac/32.png) [@Pat](https://forum.inductiveautomation.com/u/Pat)\
**Post date:** [October 15, 2015, 5:12pm UTC](https://forum.inductiveautomation.com/t/history-max-time-beetween-records-not-applied/10621/2 "2015-10-15T17:12:31Z")

</div>

Change your Max time between records to 1 Executions (instead of Seconds) which I guess to be HistoryMaxAgeMode=1, this will cause the Historian to record a value every time the Scanclass executes.

Another option to force the Historian to record a value every time the Scanclass executes is to Change the Historical Deadband to -1.0.

This issue you are seeing with a record every 2 seconds is a timing issue. The Scanclass is executing and seeing that the last record isn’t greater than one second ago, therefore no new entry, second time around the last record is greater than one second then your get a new record. You can see this issue in your query, where most of your records are 2 seconds apart, but you have a record at 14:05:13.8300 and another record at 14:05:14.8310, that scan took slightly over a second to execute hence you have a record during both of those seconds.