# Edge store and forward w/periodic data collection

**URL:** <https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879>\
**Category:** Ignition\
**Tags:** edge, scripting\
**Created:** [April 3, 2026, 1:41pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879 "2026-04-03T13:41:10Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\
**Post date:** [April 3, 2026, 1:41pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/1 "2026-04-03T13:41:10Z")

</div>

What options are there for reliably collecting periodic data with an edge device while using store and forward? Basically, I’d like to have the functionality of transaction groups but on an edge device using store and forward to minimize data loss.

Current options that I see:

- **Tag Historian + Gateway Network connection**
  - Enable tag history on tags of interest. Set sample mode to periodic.
  - Send data via gateway network to central gateway.
  - Use system.historian.queryRawPoints on a timer script to consume data on central gateway.
  - Insert data from historian into custom tables.

- **MQTT Transmission + MQTT Recorder**
  - Set up Records for tags of interest in MQTT Transmission.
  - Use a timer script to query Recorder tables and insert into custom tables on central gateway.

Is Tag Historian reliable enough to do this? I also noticed when using system.historian.queryRawPoints that many of the timestamps were 00:00, which obviously causes issues when trying to record historian data into my own custom tables.

---

<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:** [April 3, 2026, 2:02pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/2 "2026-04-03T14:02:00Z")

</div>

Edge doesn't support anything like transaction groups. The closest you can get is to use gateway messaging. You'd be completely on your own with a bespoke in-memory store and forward.

Buy a carefully trimmed standard license and deploy that instead. Really.

---

<div class="post-metadata">

**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\
**Post date:** [April 3, 2026, 4:09pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/3 "2026-04-03T16:09:17Z")

</div>

Understood about edge not supporting transaction groups. Why would Tag Historian or MQTT Recorder not be applicable for this? My understanding is that both of those support store and forward via the gateway network/MQTT Transmission.

---

<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:** [April 3, 2026, 4:13pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/4 "2026-04-03T16:13:41Z")

</div>

It isn't store and forward like Standard has. It is not record-based at all. It even has a different name: Sync Services.

---

<div class="post-metadata">

**Author:** ![Cade\_Allen](https://avatars.discourse-cdn.com/v4/letter/c/db5fbb/32.png) [@Cade\_Allen](https://forum.inductiveautomation.com/u/Cade_Allen)\
**Post date:** [April 3, 2026, 4:33pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/5 "2026-04-03T16:33:24Z")

</div>

Would scripting writes into the historian on the Edge gateway work for this? Or are the sync services prone to data loss? Just trying to understand why this wouldn’t work for periodic data collection.

MQTT Recorder seems like the next best option, given that it allows for the creation of records.

---

<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:** [April 3, 2026, 4:44pm UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/6 "2026-04-03T16:44:12Z")

</div>

Perhaps you should try.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [April 4, 2026, 1:47am UTC](https://forum.inductiveautomation.com/t/edge-store-and-forward-w-periodic-data-collection/114879/7 "2026-04-04T01:47:37Z")

</div>

> [@Cade\_Allen](#):
>
> Or are the sync services prone to data loss?

Edge Sync is **very** reliable in transferring historical data to a full gateway. Whether or not you can script a transaction using Edge Historian is up to you.
