# Ignition Edge - Buffer limitations **URL:** \ **Category:** Ignition\ **Created:** [August 2, 2025, 8:59am UTC](https://forum.inductiveautomation.com/t/ignition-edge-buffer-limitations/109281 "2025-08-02T08:59:40Z")\ **Posts on this page:** 1\ **Showing post:** 12
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [August 2, 2025, 10:31pm UTC](https://forum.inductiveautomation.com/t/ignition-edge-buffer-limitations/109281/12 "2025-08-02T22:31:56Z")
This might help: > [@Ignition Edge Local Storage Limit: What Happens When 10 Million Data Points Are Reached?](https://forum.inductiveautomation.com/t/ignition-edge-local-storage-limit-what-happens-when-10-million-data-points-are-reached/104469/7): > > As currently implemented: No later than every 60 seconds, the edge historian runs a maintenance task that finds the oldest timestamp in the historian, and then deletes all data older than (not equal to) that timestamp. There is no logic I can see to evict new incoming data eagerly, so you absolutely could exceed the row "limit" for some period of time until records are evicted. The tags.history.InternalHistorian.Engine logger on debug or trace would be informative to follow, OP. Note that Edge Sync Services are drawing from the Edge historian, so the row limit does apply to it. --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-edge-buffer-limitations/109281)._