# Store and Forward Engine on Storage only **URL:** \ **Category:** Ignition\ **Tags:** ignition83, edge\ **Created:** [December 29, 2025, 10:31am UTC](https://forum.inductiveautomation.com/t/store-and-forward-engine-on-storage-only/113008 "2025-12-29T10:31:38Z")\ **Posts on this page:** 1\ **Showing post:** 10
**Author:** ![Kurt.Larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kurt.larson/32/6426_2.png) [@Kurt.Larson](https://forum.inductiveautomation.com/u/Kurt.Larson)\ **Post date:** [April 28, 2026, 1:03am UTC](https://forum.inductiveautomation.com/t/store-and-forward-engine-on-storage-only/113008/10 "2026-04-28T01:03:48Z")
You can use both the new [Store & Forward](https://sdk.inductiveautomation.com/javadoc/ignition83/8.3.4/com/inductiveautomation/ignition/gateway/storeforward/package-summary.html) + [Historian API](https://sdk.inductiveautomation.com/javadoc/ignition83/8.3.4/com/inductiveautomation/historian/gateway/api/package-summary.html); while the Historian API is decoupled from Store & Forward, you can still create your own `DataSink` and register it against the Store & Forward engine (for your connection that needs persistence durability). The only issue is that the Historian's `TemporalPoint` data model is not an extension of `PersistentData` (Store & Forward's data modeling). What you'll end up having to do is use the bridge classes contained within the [Historian's API `interop` package](https://sdk.inductiveautomation.com/javadoc/ignition83/8.3.4/com/inductiveautomation/historian/gateway/interop/package-summary.html), which allows conversion back and forth between the new Historian API and `TagHistoryData` for Store & Forward purposes. Also check out this post for a bit more of an overview: [Historian SDK API Changes in Ignition 8.3.3](https://forum.inductiveautomation.com/t/historian-sdk-api-changes-in-ignition-8-3-3/112926) --- _[View the full topic](https://forum.inductiveautomation.com/t/store-and-forward-engine-on-storage-only/113008)._