---
title: Troubleshooting
slug: how-tos/jV2c-troubleshooting
createdAt: 2026-07-08T07:12:40.000Z
---

Most problems show up in the Ignition Gateway logs under **Diagnostics > Logs**. Filter on `FactryHistorian`. Enabling **Debug logging** on the profile adds per-call detail.

**Historian profile does not show as Running**

Usually an invalid or expired collector token, a blocked port between the gateway and Factry Historian, or a TLS trust failure. The log entry names the cause.

**TLS handshake failures**

Find out whether the Historian presents a public, internal or self-signed certificate. For an internal or enterprise CA, paste the CA into **Custom CA certificate (PEM)** on the profile rather than enabling **Skip TLS verification**. The certificate's host name must match the host carried in the collector token.

**The collector shows as inactive in Factry**

The module registers and reports health on startup and periodically. An inactive collector means the gateway cannot reach Factry Historian, or the historian profile is not running.

**Tags not appearing in Factry**

Confirm the tag's **Storage Provider** is set to the Factry profile in Ignition Designer, that **History Enabled** is true, that the tag's value actually changes, and that the module status is Running.

**Data is stored in Factry but missing from the Ignition tag browser**

Ignition refreshes its measurement cache every 30 seconds, so a newly created measurement can take that long to appear.

**A measurement has no description or unit of measure in Factry**

The tag's description and engineering range are only sent when **Include Metadata** is true on the tag, and they are only applied when the measurement is created. A tag historized before that setting was turned on keeps an empty description and unit until its measurement is recreated. Filling them in on the measurement in Factry works too.

**The tag browser shows a flat list instead of a folder tree**

Set **Tag path delimiter** to `/` on the historian profile.

**Pending count grows and never drains**

The module retests connectivity every 30 seconds. After the Historian is reachable again, forwarding resumes within that window. See [Store and forward](docId\:mHdarF-Zgdvk-NQ47go8G).

**Quarantined count grows**

Usually a data type mismatch between the Ignition tag and the Factry measurement, or an expired token. The log entry states the reason.

A measurement deleted in Factry does not normally quarantine anything: the module recreates it on the next write. It does quarantine when the recreated measurement never reaches **Active**, so check that the collector has a default time series database.

**Throughput questions**

Enable **Debug logging** on the profile. The gateway log then shows each store and query call, with the number of points and rows involved.