Repository navigation
fix(schedules): anchor purge grace window to first cron fire - #270
Merged
Merged
Conversation
harlan-github-agent
Bot
added
harlan-agent-running
Contributor
Author
🤖 MERGED
GitHub merged this pull request. No material findings were recorded. f05bd44a-2551-49fb-8b65-c2d9dbec7f26 |
harlan-github-agent
Bot
added
harlan-agent-pending
harlan-github-agent
Bot
removed
the
harlan-agent-pending
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
Closes #267
❓ Type of change
📚 Description
The nightly health report started flagging purge-personal-data on 2026-09-18T12:00Z:
False alarm. The task's grace window was anchored to its authoring date, 2026-09-17, so the 36-hour silence allowance expired four days before the deployed cron trigger's first fire at 2026-09-22T04:30Z. Until that fire the task has no run history, which the schedule policy reads as a dead trigger rather than a task awaiting its first turn.
This anchors the grace to the first cron fire instead. Once that fire lands, a run record exists and the missing_run path stops applying.
I took 2026-09-22T04:30Z as the first fire from the issue's triage of the deployed schedule, not from Cloudflare directly. Deploy first, then the issue's verification curl against /api/internal/checkin will confirm the report is clean; that could not run from here.