Skip to main content

​
Scheduling

Scheduled audits run on a cron schedule, provisioning a fresh sandbox and executing the configured audit each interval. Use them for continuous coverage between manual engagements.

​
Why schedule audits

  • Continuous coverage — catch regressions within hours, not at the next quarterly pentest
  • Compliance — produce continuous evidence for SOC 2 / ISO 27001 / PCI controls
  • Release gating — schedule a shallow audit shortly after each release window
  • Drift detection — see when a new subdomain appears or a new vulnerability surfaces

​
Creating a scheduled audit

  1. Open a workspace and click Scheduling in the workspace sidebar
  2. Click New Schedule
  3. Configure:
    • Name — e.g., “Daily shallow scan”
    • Audit type — shallow / deep / autonomous
    • Cron expression — when to run
    • Targets — defaults to workspace domain
    • Scope — required only for autonomous type
  4. Click Save
The next run time appears immediately. Schedules are active by default.

​
Cron syntax

Golem AI uses standard 5-field cron:
Common patterns

​
Choosing a cadence

Shallow audits are designed for frequent runs. Deep and autonomous audits consume significant compute — schedule them weekly or less often unless you specifically need higher frequency.

​
Managing schedules

From the Scheduling page you can:
  • Pause a schedule without deleting it
  • Edit the cron expression, audit type, or scope
  • Run now to trigger an ad-hoc audit outside the schedule
  • View runs to see past audits triggered by this schedule
  • Delete the schedule (does not affect past audit history)

​
Notifications

When a scheduled audit completes, Golem AI can notify via:
  • Email — sent to your account email by default
  • Slack — if Slack is connected
  • Webhook — if callbackUrl is configured on the schedule
Notifications include the audit score, finding counts, and a direct link to the report.

​
Concurrency

Scheduled audits respect your plan’s concurrent audit limit. If a schedule fires while you’re at capacity:
  • The scheduled run queues until capacity frees
  • If the queue exceeds the configured timeout, it fails with CONCURRENCY_LIMIT_EXCEEDED
For continuous shallow scans across many workspaces, the Max plan removes the concurrency cap.

​
Next steps

Slack Integration

Route schedule notifications to a channel.

Scheduled Audits API

Manage schedules programmatically.