Revalidate published custom query tables nightly
What It Does
The nightly revalidation schedule fires at 04:20 UTC, or staff request the same bounded pass.
The Flow
Invoke the revalidation pass from the schedule or staff route. Check validation-workspace configuration and log a skip if it is absent. Reanalyze active or deprecated released versions and pinned versions, comparing source-derived and stored fingerprints.
When Something Fails
Undelivered invocation reaches its dead-letter handling; missing runs trigger the silence alarm. A newly broken table can remain undiscovered until another validation or execution. The configured skip completes without analyzing tables. That environment receives no revalidation coverage. Record failing health with problem codes rather than SQL or record contents. The version’s health indicates the failure; no automatic repair is supplied.
Idempotency and Concurrency
Health-change history is retained, with passing history bounded to one entry per version per day. Repeating a pass does not mean it performs no validation work. Revalidation is a bounded scheduled operation rather than a durable job; later passes replace interrupted work.