Audit will not rerun

Symptom

The run action is unavailable, an automatic audit does not start, or the latest result continues to show an older commit.

Check for a new commit

Recurring audits are intended to evaluate new repository state. If the repository has not changed since the last completed run, Guard may not create a duplicate run.

Compare the latest repository commit with the revision shown in audit history.

Check current work

An audit may already be queued or running. Wait for that run to finish before expecting another run for the same audit and repository.

Check the schedule

Confirm that:

• automatic runs are enabled;
• the current day is eligible;
• the configured time window uses the expected timezone;
• cooldown has elapsed;
• inactivity has not paused the schedule.

Review Configure recurring audits for the full scheduling model.

Check provider access

Expired GitLab tokens, changed GitHub App installation access, or an unreachable self-hosted GitLab host can stop new evidence collection.

Restore connection health before retrying the audit.

Check product limits

Demo access limits repeated runs and automation. Confirm that the project and audit are eligible for another run under the current plan.

If the problem remains

Record the project, repository, audit name, expected commit, visible status, and approximate time. Do not include access tokens, private report content, or repository secrets in a support request.