Stop guessing why the trend went blank.
Historian problems get muddy fast: the current tag is Good, the chart is blank, a query returns buckets, and store-and-forward may still be catching up. This skill makes the AI separate stored data from queried and rendered data before it names a cause.
Why it was made
- Separates storage, delivery, query settings, and chart rendering instead of treating every blank trend as missing data.
- Keeps deadband, quality, interpolation, retention, pruning, timezone, and tag identity assumptions visible.
- Starts read-only, so the AI does not jump to backfills, quarantine retries, cache clearing, or historian-table edits.
Common use cases
- Power Chart, Easy Chart, or Perspective history bindings with blank, flat, delayed, or sparse data.
- Good current values that do not prove the historical rows were stored.
- Store-and-forward, quarantine, database connection, pruning, or retention questions.
- Historian identity problems after tag renames, provider changes, backfills, or duplicate historical entries.
Proof style
Validate the artifact, not the promise.
The skill does not guarantee recovery or root cause from a screenshot. It asks for tag, quality, history, database, log, time-window, and chart-setting evidence before naming a cause. Raw historian SQL is reserved for deliberate database forensics.
Evidence
Historian evidence workflow proof
The graphic is AI-generated for the site. The checks below come from sanitized historian-forensics evidence: official Ignition 8.1 documentation checks, static contract tests, live read-only runner probes, option-gap tests, red-team report grading, and source-versus-product packaging checks. The skill is built to investigate evidence; it does not promise data recovery, automatic historian repair, or regulatory proof without the target evidence.
- Live read-only probes exercised health, gatewayInfo, databaseConnectionsList, tagProviders, tagBrowse, tagRead, historyProbe, and focused logQuery on Ignition 8.1.53.
- A current tag read with Good quality was kept separate from history availability, because current value does not prove historical storage.
- historyProbe returned timestamp buckets with null value cells in one run, proving row count alone is not stored-value evidence.
- Negative path testing rejected an unqualified historyProbe path with a bounded 400 response.
- Red-team report tests preserved contradictions and blocked root-cause or remediation claims until the needed historian evidence exists.
Example prompt
Diagnose why [default]Line1/Press/Temperature is blank in a Perspective Power Chart for yesterday, even though operators say the value was live all shift.This is the kind of short instruction the skill is designed to make useful. The value is in the checks and Ignition-specific defaults the AI uses after reading the skill.
Expected output
- Checks the current tag read, history-enabled/provider evidence, query window, chart binding settings, and store-and-forward context separately.
- Treats chart output as rendered evidence, not raw historian storage proof.
- Recommends the next read-only proof step before any tag, cache, quarantine, backfill, or database change.
Related workflows
Skills that pair with this one
Lifetime membership
Want access to this skill?
The one-time membership unlocks this skill, the full Ignition AI Toolkit, the Web Dev runner materials, setup docs, versioned downloads, and future Ignition 8.3 skills as they ship.
No subscription. Lifetime members keep portal access to the current toolkit and future skill releases, including planned Ignition 8.3-focused skills as they are added.