Report Intervals

Minimum re-reporting intervals — advisory suppression of repeat findings, so a persistent problem is surfaced once per interval rather than once per run. Defined against the check only, like thresholds — one value per check, applying wherever the check runs. Evaluation itself is never suppressed: the evaluation engine stamps each evaluation's reportable flag (any severity change, in either direction, always reports; only the same severity repeating inside the interval is suppressed; skipped rows never report), and every consumer chooses whether to honour it — see Minimum Report Intervals in the User Guide for the narrative, and p_reportable_only on the two reporting functions. Like thresholds, the interval is deployment tuning: it works directly on built-in checks, and — like thresholds — is reset on every catalog reseed (pghf.seed_data() seeds a default per built-in check, keyed off its cadence-suite membership; see Catalog Seeding). Like blackouts, it also works under an inactivated namespace or category.

pghf.set_report_interval(p_check_id text, p_minutes integer)

Sets or clears a check's minimum re-reporting interval.

Parameter	Type	Mandatory	Default	Description
p_check_id	text	Yes	—	Must exist. Built-in checks allowed — the definition lock on built-ins does not apply here.
p_minutes	integer	Yes (may be empty)	—	Minutes, zero or more. Empty clears (no suppression); 0 = always report.

Returns: nothing. Only a role explicitly granted permission — whichever tunes reporting in your deployment — can call this.

pghf.get_report_interval(p_check_id text)

The check's interval in minutes — exactly the value the evaluation engine's stamping uses.

Parameter	Type	Mandatory	Default	Description
p_check_id	text	Yes	—	Must exist.

Returns: integer — empty means no suppression is configured. Callable by anyone.