Skip to main content
Scheduled runs start Cloudgeni agent sessions automatically from a workspace schedule. Use them when you want the same agent instructions to run repeatedly against selected repository, cloud, or documentation context.

What you need first

  • Organization admin or workspace admin access
  • A workspace with the repositories or integrations the agent will use
  • An agent and instructions that make sense to run more than once
Scheduled runs are workspace scoped. A schedule can only use context connected to the workspace where it is created.

Create your first schedule

The animation below shows how recurring agent instructions, cadence, timezone, and workspace context fit together, then how runs appear in history and the workspace automation overview.
  1. Open the workspace where you want the run.
  2. Open DevOps Agent.
  3. Open Scheduled runs in the agent sidebar.
  4. Click New schedule.
  5. Choose the agent, instructions, cadence, time, timezone, and context.
  6. Click Create.
  7. Select the schedule and click Run now to test it.
  8. Open History, then click Open session.

What to schedule

Good first schedules are narrow and repeatable:
  • Daily infrastructure context check
  • Weekly repository review
  • Recurring drift investigation
  • Follow-up over selected cloud and documentation context
Avoid broad instructions such as “review everything”. Scheduled runs work best when the instructions name the repository, risk area, or check you want repeated.

Review and manage runs

Each scheduled or manual run creates an agent session. Use the schedule history to open the session, read the result, and continue the conversation if needed. From the scheduled runs page you can:
  • Run now
  • Pause or resume
  • Edit the instructions, time, timezone, or context
  • Delete the schedule

What to expect

  • Run now starts the same workflow as the next scheduled time.
  • If the previous linked session is still active, Cloudgeni skips the next run to avoid overlap.
  • A schedule cannot use repositories or integrations from another workspace.

Troubleshooting

SymptomWhat to check
Scheduled runs is not visibleConfirm the user can access the workspace, then refresh the app.
A repository or integration is missingConfirm it is connected to the same workspace where you are creating the schedule.
The schedule did not launchCheck history for skipped or failed status.
A run was skippedCheck whether the previous linked session is still active.
The next run time looks wrongCheck the timezone and cadence.
Open session is unavailableThe linked session is no longer available to the current user.

AI DevOps

Learn how agent sessions use selected context.