# Caching data on loss of connection to historian

**URL:** <https://forum.inductiveautomation.com/t/caching-data-on-loss-of-connection-to-historian/108135>\
**Category:** General Discussion\
**Created:** [July 4, 2025, 8:29am UTC](https://forum.inductiveautomation.com/t/caching-data-on-loss-of-connection-to-historian/108135 "2025-07-04T08:29:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Gavin\_Bentley](https://avatars.discourse-cdn.com/v4/letter/g/8c91f0/32.png) [@Gavin\_Bentley](https://forum.inductiveautomation.com/u/Gavin_Bentley)\
**Post date:** [July 4, 2025, 8:29am UTC](https://forum.inductiveautomation.com/t/caching-data-on-loss-of-connection-to-historian/108135/1 "2025-07-04T08:29:05Z")

</div>

Can Ignition cache data if the connection to the historian db is lost ?

For example if Ignition is monitoring customer consumption on end of line power circuits and the connection to the TimescaleDB is lost will the data be lost or can it be cached in Ignition for a set time until the connection is restored to the TimescaleDB ?

---

<div class="post-metadata">

**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:** [July 4, 2025, 1:22pm UTC](https://forum.inductiveautomation.com/t/caching-data-on-loss-of-connection-to-historian/108135/2 "2025-07-04T13:22:28Z")

</div>

If you are using Ignition's historian, it will cache collected data in its Store and Forward system and push it through when the DB connection is restored. The store and forward subsystem is optional for various other DB operations (INSERTs and UPDATEs only) that can "fire and forget" their operations.