Decide when Guard should check new commits and understand why an unchanged repository may not rerun.
Documentation · Updated July 30, 2026
Before you enable recurrence
Complete base diagnostics and at least one relevant audit before turning on recurrence. Confirm that Guard can still read the repository and that the latest completed result refers to the commit you expect.
Recurring audits are useful for repositories where new code can move a metric out of the green zone. They are not required to produce a good score, and enabling recurrence does not change the result of the audit that already completed.
Choose a cadence
Open the selected audit metric and use Rerun to reach Restart and automation. In Automatic runs, enable Run automatically when code changes, then choose the cadence that matches the repository’s change rate: Daily, Workdays, Three times a week, Twice a week, Once a week, or Monthly.
Weekly patterns use Days of week. Monthly recurrence uses Day of month. The audit auto-run control uses the browser-resolved timezone in the schedule hint, and the saved audit automation window runs once on the chosen day when a new commit is waiting. Treat that setting as eligibility for useful new work, not a promise to create duplicate reports.
Restart and automation
Run this audit now or after new code changes.
Close
Automatic runs
Enji Guard checks for new commits about every 3 minutes and starts the next audit on the day you choose.
Run automatically when code changes
Enji Guard checks new versions on the selected cadence and runs only when the commit changed.
Timing
Days of week
Runs once on the chosen day when a new commit is waiting. More commits wait for the next eligible day. Timezone: UTC.
Autofix
Dependency hygiene · Dependency update
Close
The agent fixes one critical problem per run.
How it works
Auto-improvementsOn
Dependency update
Enji Guard will automatically and regularly create tasks and PRs to improve this metric.
Get notifications
GitHub IssueOne issue per run
Pull RequestWith code fix
Days of week
Audit auto-runs and Autofix scheduling adapted from the Upfront controls. Fictional state.
Enable automatic runs
Open the score or metric action for the audit you want to keep current.
Open Rerun, then review the Run once now area before changing automation.
Turn on Run automatically when code changes.
Choose the cadence and, when shown, the eligible weekdays or month day.
Check the timezone hint.
Save the schedule.
Review Email me about if you want completion mail for manual reruns or automatic audits after code changes.
The schedule belongs to the selected audit metric. Enabling recurrence for Security does not automatically schedule Dependency hygiene, Tests, AI readiness, or any other audit for the same repository.
What triggers useful new work
Guard observes the repository head and starts the selected audit only when there is newer repository state to check. When the current head is already the last successfully audited head, the rerun path can remain unavailable with the unchanged-repository explanation instead of producing duplicate evidence.
After an automatic run starts, Guard waits for the next eligible cadence slot before it reacts to another new commit for that audit. Existing active work, repository access, account limits, hidden audit settings, and missing source context can also prevent a run from starting. Use What starts a run for the broader trigger model.
Verify the result
Open audit history after the next eligible run and confirm the checked commit, completion state, current score, and changed evidence or limitations. The schedule tells Guard when to look for new work; the completed audit result tells you whether the repository moved toward or stayed in the green zone.
Audit
Overall scoreHealthy↑ 12 vs last time
Audit history keeps each completed score tied to a run so later verification starts from evidence, not from the schedule setting. Fictional data.
Return to the same metric’s Restart and automation controls to change cadence or disable automatic runs. Disabling future eligibility does not delete completed audit history.
If you are stopping recurrence because a repository is archived, disconnected, or intentionally inactive, keep the last report as historical evidence and read it against its recorded commit.
Enji Guard