Why a Remote Historian can show old trends but not store new data
If old trends load but new history is not accumulating, separate Remote Historian read capability from storage capability.
Start with the symptom
If old trends load but new history is not accumulating, separate Remote Historian read capability from storage capability.
What the documentation establishes
In Ignition 8.3, Storage Allowed=false makes the Remote Historian query-only; it does not send new data for remote storage.
With Storage Allowed=true, the provider creates a Store and Forward pipeline to send data to the remote Gateway.
Five checks at a glance
| Scene | Point | Limit |
|---|---|---|
| 1 | Historical query ≠ new history storage. | Historical query and new-history storage are separate capabilities. |
| 2 | Storage Allowed=false → query only. | Query is allowed; new data is not sent for storage by this provider. |
| 3 | Storage Allowed=true → Store and Forward pipeline. | Enabling storage creates a Store and Forward pipeline to the remote Gateway. |
| 4 | 0 = unlimited points per request, not unlimited storage. | Zero means no point-count limit per remote request, not unlimited storage capacity. |
| 5 | Read the provider and storage setting before changing anything. | Read-only setting check; no live Gateway write test. |
Do not over-interpret the symptom
Max Group Size=0 means unlimited data points per remote request; it is not an unlimited history-storage-capacity claim.
Read-only preflight
- Historical query ≠ new history storage.
- Storage Allowed=false → query only.
- Storage Allowed=true → Store and Forward pipeline.
- 0 = unlimited points per request, not unlimited storage.
- Read the provider and storage setting before changing anything.
Evidence limits
A visible old trend does not prove new writes are enabled. Check the actual provider and Storage Allowed setting read-only. No live Gateway was tested.
This article interprets first-party documentation and uses hypothetical diagrams. It does not report a live device, database, customer-data, outage, recovery or performance test.
Watch the short explanation
The public YouTube schedule may be linked here after the provider assigns the native video ID. The article and local video are already self-contained.