> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudgeni.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Scheduled runs
> Run an agent session on a schedule inside a workspace, then review the result like any other session.
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`.
```mermaid actions={false} theme={null}
flowchart TD
setup["Create schedule\nagent, instructions, time, context"] --> start{"Start method"}
start -- "Run now" --> session["Agent session"]
start -- "Recurring time" --> session
session --> history["History\nOpen session"]
classDef action fill:#EFF6FF,stroke:#2563EB,color:#1E3A8A;
classDef decision fill:#FEF3C7,stroke:#D97706,color:#78350F;
classDef success fill:#ECFDF5,stroke:#047857,color:#064E3B;
classDef data fill:#F8FAFC,stroke:#64748B,color:#0F172A;
class setup action;
class start decision;
class session success;
class history data;
```
## 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
| Symptom | What to check |
| -------------------------------------- | ---------------------------------------------------------------------------------- |
| `Scheduled runs` is not visible | Confirm the user can access the workspace, then refresh the app. |
| A repository or integration is missing | Confirm it is connected to the same workspace where you are creating the schedule. |
| The schedule did not launch | Check history for skipped or failed status. |
| A run was skipped | Check whether the previous linked session is still active. |
| The next run time looks wrong | Check the timezone and cadence. |
| `Open session` is unavailable | The linked session is no longer available to the current user. |
## Related pages
Learn how agent sessions use selected context.