Data health

Every stored series checked against published review triggers. A flag means a person should look; nothing is changed, hidden or fixed automatically.

Checked against 17 Oct 2026 · Data ↓

Series

633

A series can carry several flags, so the buckets can add up to more than the total.

By source

Loader	Series	Last successful refresh	Runs (30d)	Failed runs	Failing now	Stale
cockpit file	540	30 Sep 2026 09:08 UTC	1	0	0	250
direct_fred	5	17 Oct 2026 05:44 UTC	64	2	0	0
direct_yahoo	34	17 Oct 2026 05:44 UTC	64	2	0	0
idx_ic IDX (robots.txt) refused the request (HTTP 403); the site may block automated requests from this network	0	never	62	62	1	0
securities_yahoo	43	17 Oct 2026 03:13 UTC	47	2	0	0
us_spdr	11	17 Oct 2026 03:15 UTC	62	2	0	0

Series

0 series, most serious first

Nothing in this view.

Missing

Series the app refers to (in its configuration or in something people saved) that have no stored values. A country pillar without a series is “not covered” by design and is not listed.

Series	Why	Used by
`AADI.JK`	referenced, never stored	IDX security master: AADI
`MTEL.JK`	referenced, never stored	IDX security master: MTEL
`sec_id_energy`	referenced, never stored	Workspace template: Indonesia Equity
`sec_id_financials`	referenced, never stored	Workspace template: Indonesia Equity
`sec_id_basic`	registered by a loader, no values stored
`sec_id_industrials`	registered by a loader, no values stored
`sec_id_noncyclicals`	registered by a loader, no values stored
`sec_id_cyclicals`	registered by a loader, no values stored
`sec_id_healthcare`	registered by a loader, no values stored
`sec_id_property`	registered by a loader, no values stored
`sec_id_technology`	registered by a loader, no values stored
`sec_id_infrastructure`	registered by a loader, no values stored
`sec_id_transport`	registered by a loader, no values stored

How this is checked, and the review triggers in use

Data Health Console (Sprint 5). Checks every stored series against published review triggers
(config/data_health.yaml) and never changes the data.
    STALE        newest reading older than the allowance for its frequency; or flagged stale by the cockpit
                 file's own source checks
    FAILED       the latest run of the connector that loads the series reported an error for it
    SUSPICIOUS   impossible or non-finite values (a non-positive level in a series measured in % changes),
                 two different values for one date in a single load, an unexpected gap, a large
                 discontinuity (robust z of a one-reading change)
    MISSING      referenced by the app (configuration or something people saved) but not stored
A series can carry several flags; HEALTHY means none. Per source: each loader (the cockpit file or a fetch
connector) with its last successful refresh, failed runs in the window and the stale series it loads.

Stale after (days, by frequency d/w/m/q)	7 / 14 / 75 / 160
Unexpected gap (days, d/w/m/q)	14 / 21 / 62 / 123
Large discontinuity	robust z ≥ 12, 730 days, at least 30 changes

Edit config/data_health.yaml to change them.