config.ageBy names the clock `maxAge` reads, and this panel sets no `maxAge`, so nothing reads it - add `maxAge` (ms) to say how long the panel waits before it stops grading what it holds.

Warnings reference › kpi:ageBy-no-maxAge

Identifier

kpi:ageBy-no-maxAge

Raised by

KPI

Since

1.70.0

What happened

ageBy says which timestamp counts as a row's age, and maxAge says how old is too old. Only maxAge starts the freshness machinery, so ageBy on its own has no reader: the panel grades every tile as usual and will never report a silent feed. The pair is deliberately opt-in - inventing a default window would make every existing panel start reporting silences.

The fix

Add maxAge in milliseconds alongside ageBy.

The smallest fix

createKPI(el, { rows, tiles, ageBy: 'updatedAt', maxAge: 60000 });

Reference

Covered in full at the API reference.