feat(cron): add durable execution audit history - #61791
Merged
Merged
Conversation
teknium1
force-pushed
the
feat/cron-execution-ledger
branch
from
July 13, 2026 06:51
4a20390 to
49b375f
Compare
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.
Summary
Cron execution attempts now have bounded, indexed, restart-safe audit history with truthful unknown outcomes and an operator inspection surface.
Changes
claimed → running → completed/failed/unknownattempts in profile-localcron/executions.dbbefore executor/provider dispatch.hermes cron runs [job-id] --limit N/history, quick-backup coverage, and English/Chinese docs.Validation
unknown; no retry manufactured; CLI showed original IDgit diff --checkThis PR is intentionally held unmerged for soak and review after CI.
Infographic