All times UTC.
The seal job runs at 04:00. The feeds are validated much earlier, but their validation reports are only written into the database as the night goes on — process-validation-report works through them one at a time and doesn't finish until about 08:30.
Feeds whose report hasn't been written yet get UNKNOWN for compliant, fresh_coverage and fresh_continuous, and keep yesterday's verdict.
On 2026-09-29 that was 397 feeds, and 6 of them showed a failure their own data contradicts — mdb-2411 displayed a coverage failure while its dataset covers service until September 2027.
Fix
In infra/functions-python/vars.tf, change seal_orchestrator_schedule from 0 4 * * * to 0 9 * * *.
All times UTC.
The seal job runs at 04:00. The feeds are validated much earlier, but their validation reports are only written into the database as the night goes on — process-validation-report works through them one at a time and doesn't finish until about 08:30.
Feeds whose report hasn't been written yet get UNKNOWN for compliant, fresh_coverage and fresh_continuous, and keep yesterday's verdict.
On 2026-09-29 that was 397 feeds, and 6 of them showed a failure their own data contradicts — mdb-2411 displayed a coverage failure while its dataset covers service until September 2027.
Fix
In infra/functions-python/vars.tf, change seal_orchestrator_schedule from 0 4 * * * to 0 9 * * *.