Automation is paused

Symptom

Recurring audit reruns or Autofixes are off, Guard shows an inactivity or backlog pause, or new commits exist but scheduled work has not resumed.

Quick checks

• Read the pause banner and date.
• Check whether the pause applies to one Autofix job or repository-wide automation.
• Inspect open provider issues and PRs/MRs.
• Confirm repository access and current plan eligibility.
• Confirm the schedules were enabled before the pause.

Diagnose backlog pause

Autofix warns at 5 open PRs/MRs, 10 open issues, or 14 days for the oldest open item. It pauses at 10 open PRs/MRs, 20 open issues, or 30 days for the oldest item. Existing provider artifacts remain open. The pause protects review quality; it is not resolved by hiding the banner.

Work through or close obsolete items, starting with the oldest and highest-risk. Compare each artifact with the current default branch before deciding.

Diagnose inactivity or access pause

A quiet repository can have audit reruns and Autofixes turned off while manual audits remain available. New changes may be detected without automatically resuming schedules. Provider access loss, account limits, or a runbook safety condition can also prevent work, but those causes should appear as their own status rather than being mistaken for backlog.

Resume safely

Use Re-enable Autofix for a backlog-paused job after the provider queue is under control. Use Resume automation for repository inactivity. Then verify every intended audit and improvement schedule, frequency, timezone, and write behavior. The next run revalidates current state instead of replaying a pre-pause patch.

Escalate safely

Provide the repository, pause type and date, current open issue and PR/MR counts, oldest-item date, schedule state, and redacted error text. Never include tokens or private report content. If the visible thresholds and recorded pause reason disagree, support can inspect the backlog snapshot.