Hey there, after upgrading an ignition edge instance from 8.1 to 8.3 I got an error regarding the edge historian engine. Under the Store and Forward Engines menu, the edge historian status displays “storage only“. The Gateway logs for the edge historian engine give me the info: Skipping validation…

Actually, I want to jump in here and clarify how this works on Edge specifically, as the status screen can be quite misleading in 8.3. The "Storage Only" status you are seeing is actually expected behavior and does not indicate that your sync to the central gateway is broken. Here is the technical…

The “Storage Only” status means that after upgrading from 8.1 to 8.3. The edge device is holding data locally and because it may be having issue syncing the data to the main gateway. This could be caused by a number of reasons: such as the historian sync not being enabled firewalls blocking data m…

@anjoroge , @Kurt.Larson Thank you for the reply and the detailed explanation. That makes it easier for me to understand. After trying some different network configurations the two gateways worked correctly again. Regarding this subject I still have one more question for clarification. On the edg…

That is a great observation and it perfectly illustrates the architectural difference I mentioned. Here is the breakdown of why those metrics look different on each side: 1. On the Edge Gateway (Metrics are 0) As you noted, the Store & Forward metrics (store rate, forward rate, etc.) are all 0. T…

I've got it now. Thank you for the detailed explanation!

How would that work for new third party modules that are implementing the new historian api? How would they do store and forward? Would they have to use the legacy store and forward? Or what is the best practice here?

I really want to know, would someone know the answer to my question? Replying again to bump it up :slight_smile: .

You may be blazing a trail on the new API. I haven't studied it yet.

You can use both the new Store & Forward + Historian API ; 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…

Hi Kurt , thanks so much for the answer. On 8.3.4 version Its any way to access the Edge S&F settings that were on 8.3.1 version. Where those settings get stored ? For example the following settings Maintenance Settings Setting Description Primary Store Maintenance Value The maximum am…

See Kurt's answer for that over here: [image] 8.3.5 pulled, 8.3.6 Emergency Release Ignition The Store & Forward metrics page was in fact removed in 8.3.3 as it was misleading; Edge doesn't leverage Store & Forward for its local data storage. You can find more …

Store and Forward Engine on Storage only

Ignition

pturmel April 28, 2026, 4:45pm 12

See Kurt's answer for that over here:

Whatever you might have been doing with those didn't actually affect your Edge storage.