Files
hledger-web-reports/.changeset/purge-expired-query-workflows.md
eleith 6140209ea6
ci/woodpecker/pr/jobs Pipeline was successful
ci/woodpecker/pr/web Pipeline was successful
ci/woodpecker/pr/worker Pipeline was successful
ci/woodpecker/push/jobs Pipeline was successful
ci/woodpecker/push/web Pipeline was successful
ci/woodpecker/push/worker Pipeline was successful
feat: retain query jobs with a jittered daily SDK schedule
2026-10-20 21:25:33 -07:00

1016 B
Raw Permalink Blame History

@hledger-reports/worker
@hledger-reports/worker
patch

Schedule query-job retention through OpenWorkflow's native recurring support at 00:MM UTC daily, with minute 1–59 sampled once per worker startup. No custom timer or YAML setting is added. The stable schedule preserves administrative pauses; changing its minute reschedules the next occurrence rather than guaranteeing overdue catch-up.

Each run uses one atomic DELETE to remove up to 100 finished, standalone query records strictly older than seven days by completion time. Active, related, keyed, step/signal-bearing, scheduled and unknown work is preserved; larger backlogs can remain longer. Only aggregate deletion counts are stored by maintenance.

Existing journal, price, snapshot, legacy capture/result files and backups are untouched. This is logical SQLite retention, not secure erasure or guaranteed file shrinkage. Operators who need old job history should take a consistent backup before deploying. Restarts with a changed cron minute may postpone cleanup.