Hi everyone, I wanted to share an issue I ran into while working with Ignition and the Core Historian, and also ask if anyone has seen something similar or has any recommendations.
On a Gateway running Ignition 8.3.1, the Core Historian provider showed a RUNNING status with no visible errors. Tags could be configured and historized without any issues, but when trying to view the data in PowerChart, no historical values were shown and the message “No Trend Data Source available (Bad_NotFound)” appeared.
I tried several things without success, including disabling and re-enabling the Historical Provider, creating new tags and historizing them, restarting the Gateway, and deleting and recreating the Historical Provider. None of these actions changed the behavior.
While reviewing the Core Historian database, I noticed there were around 16 million records and that the last stored value was from 2025-12-17 , which made it look like the historian had stopped writing new data. The provider was configured with one year of retention per partition, so I started to suspect that some internal file limit might have been reached or that one of the historian files had become locked or corrupted.
Before taking more invasive actions, I believe a good practice in this situation would be to export the existing historical data directly from the Core Historian database (for example from the core_historian.datapoints table), either completely or filtered by a date range, in order to preserve the data.
The solution I applied (clarifying that this was done only in a test environment) was to stop the Ignition service, move the Core Historian files to the backup folder, and then start the service again. After restarting, Ignition automatically recreated the Core Historian files and the historian started working again, with data correctly visible in PowerChart.
My question to the community is whether anyone else has encountered this Core Historian behavior when dealing with large data volumes, and if there are any official recommendations or best practices to avoid reaching this state (for example retention settings, partitioning, or known limits of the Core Historian).
Any feedback or similar experiences would be greatly appreciated. Thanks!