You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
purge-personal-data alarms missing_run before first fire #267
purge-personal-data's activeFromSeconds (2026-09-17, authoring date) expires its 36-hour grace four days before the deployed task's first cron fire (2026-09-22T04:30Z), so the nightly health report raises a false missing_run alarm.
The daily-checkin routine opened this issue automatically on its 2026-09-21T21:40:00.000Z run. It is not Harlan's own report. Close it to reject the proposal, and the reason you give stops it being offered again.
Summary: Confirmed in shared/schedule-policy.ts:65. activeFromSeconds 1789603200 is 2026-09-17T00:00Z; grace (36h maxSilenceSeconds) ends 2026-09-18T12:00Z, but the first purge-personal-data cron fire is 2026-09-22T04:30Z (epoch 1790051400). In that
Next action: In shared/schedule-policy.ts:65 change activeFromSeconds from 1789603200 to 1790051400 (2026-09-22T04:30Z, the first cron fire), deploy, then run the issue's curl against /api/internal/checkin and assert skilld.daily-health's reason no longer contains purge-personal-data.
Activity
harlan-github-agent commentedon Sep 21, 2026
🤖 ISSUE TRIAGE