> ## Documentation Index
> Fetch the complete documentation index at: https://docs.befailproof.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Audit cadence

> Choose when recurring audits run and how much data they review.

Use recurring audits for failure modes that can return as agents, prompts, tools, and models change.

## Change the schedule

<Tabs>
  <Tab title="Dashboard">
    1. Go to **Analyze → Audits** and open the audit.
    2. Open its settings and change the enabled state, interval, UTC anchor, window mode, or lookback.
    3. Save the audit and confirm the next-run time on the audit card.
    4. Use **run now** once after a major scope or context change.

           <img src="https://mintcdn.com/exosphere/WgPwQzedeDNwJBTy/images/dashboard/audit-edit.png?fit=max&auto=format&n=WgPwQzedeDNwJBTy&q=85&s=3bb70a9d5b24b58e3d16222980ec73d5" alt="The audit editor showing cadence, sweep window, scope, analysis settings, context, and notification channels." width="1279" height="879" data-path="images/dashboard/audit-edit.png" />
  </Tab>

  <Tab title="CLI">
    ```bash theme={null}
    fp audits edit checkout-reliability \
      --schedule-interval-secs 86400 \
      --schedule-anchor 2026-08-15T09:00:00Z \
      --lookback-window-secs 86400 \
      --yes

    fp audits edit checkout-reliability --disabled --yes
    fp audits edit checkout-reliability --enabled --yes
    ```

    See the [`fp audits` reference](/reference/cloud-cli#audits) for schedule bounds, window behavior, and all audit commands.
  </Tab>
</Tabs>

Choose cadence from the speed and cost of the risk:

| Risk pattern                   | Starting cadence |
| ------------------------------ | ---------------- |
| High-impact production action  | Daily            |
| Workflow or model regression   | Weekly           |
| Governance or access review    | Monthly          |
| One-time release investigation | Run once         |

Align the lookback window with the cadence so runs neither leave gaps nor repeatedly examine an unnecessarily large population. After changing an audit's goal or context, run it manually once before relying on the next scheduled result.

<Note>
  Local scheduled audits are configured on the machine and scan local agent history. Cloud audit schedules operate on Cloud sessions. Treat their results and ownership separately.
</Note>