Recurring execution
A scheduled run creates an investigation-style thread, preserving output, evidence, and any follow-up context.
Scheduled jobs run recurring agent work on a cadence: hygiene checks, audits, operational reviews, evidence collection, or recurring investigations. They are useful when a team wants durable automation but still wants the work expressed as an agent-run thread.

What this page covers
Create schedules with a target agent, prompt, cadence, ownership, and sharing model.
Use scheduled jobs for recurring checks that need interpretation, summarization, or follow-up recommendations.
Share jobs with users or groups so operators can inspect, run, edit, or manage recurring automation based on grants.
Operational detail
Scheduled jobs run recurring agent work on a cadence: hygiene checks, audits, operational reviews, evidence collection, or recurring investigations. They are useful when a team wants durable automation but still wants the work expressed as an agent-run thread.
A scheduled run creates an investigation-style thread, preserving output, evidence, and any follow-up context.
Operators can ask through chat to design a recurring job when the agent can translate intent into a schedule.
Scheduled-job visibility and actions follow owner, admin, and resource-grant permissions.
Related pages