Schedules and Quotas

Site Audit supports automated execution patterns to run checks periodically. You can schedule audits and track your resource consumption using built-in quota dashboards.

Scheduling audits

You can configure projects to run automatically at set times. All recurring schedules use the FULL run type to ensure consistency.

Before you start

• Schedules are processed in Coordinated Universal Time (UTC).
• Only one active workflow can run per project at any given time. Concurrency is strictly rejected: if a scheduled run triggers while an audit is already running for the project, it is immediately rejected with a concurrency conflict (409 Conflict), rather than queueing.

Steps

To add or manage schedules:

1. Navigate to your project workspace.
2. Select the Schedules tab.
3. Select Add Schedule.
4. Choose the schedule frequency:
   • Daily: Triggers once every 24 hours at a selected UTC hour.
   • Weekly: Triggers once per week on a selected day and UTC hour.
5. Select Save.

To temporarily disable a schedule, select the toggle switch in the schedules list. To permanently remove a schedule, select the trash icon.

---

Quotas and limits

Executing audits consumes system compute, network, and API resource limits.

Monthly entitlement (audit.runs_per_month)

• Every audit execution (manual or scheduled) consumes one run credit.
• Your account has an assigned monthly entitlement called audit.runs_per_month.
• The current consumption and remaining credits are visible at the top of your Site Audit dashboard.
• Credits reset on the first day of each calendar month. Unused credits do not roll over.

Concurrency gates

To prevent network abuse and platform saturation, Mincemeat applies these safety thresholds:

• Per-project concurrency: A project can run only one audit job concurrently. If you trigger an audit while a job is already active (status QUEUED, DISPATCHING, or RUNNING), the request is immediately rejected with a 409 Conflict (Toast: Another audit job is already running for this project). There is no queueing.
• API rate limits: Manual audit triggers are subject to standard account rate limiting. If rate limits are exceeded, the UI displays a 429 Too Many Requests toast notification.

Troubleshooting

Problem	Possible cause	What to do
Run button is disabled	You have exhausted your monthly credit allowance (audit.runs_per_month is 0).	Contact your Mincemeat administrator to request a quota increase.
Scheduled run missed	Concurrency conflict.	Check if a manual run was actively executing at the scheduled time. The scheduled job is rejected with a conflict error rather than queued. Ensure manual runs are not started close to scheduled windows.
Schedule times are off	Timezone difference.	Check that you configured the schedule using UTC, not your local computer's timezone.