> Source: Onevium official documentation
> Article: Create and verify scheduled automations
> Original URL: https://onevium.com/docs/scheduled-runs
> Language: English
> Updated: 2026-09-09
> Applies to: 1.1.22+

---

# Create and verify scheduled automations

Schedule recurring work, choose its conversation mode, test a run, and inspect history and notifications.

## Repeat a useful task

An automation runs a prompt in a project on a schedule and keeps its conversation and run history. Start with a documentation report, then add channel delivery if needed.

## Understand unattended execution

Run the task once in ordinary chat and confirm its project and model work. Keep Onevium and the computer available at the scheduled time.

**The Create/Edit Automation dialog saves Full Access and has no permission picker.** The scheduler preserves an explicitly configured Auto profile from other supported paths, but other profiles run as Full Access. Do not expect unattended work to wait for the same approvals as an interactive Default session. Choose a project and task appropriate for that execution mode.

## Create a documentation check

Open **Automations → Create automation**. The composer command **/loop** opens the same creation dialog; it is not Claude Code's interval-loop behavior.

| Field/control    | Example and effect                                                                        |
| ---------------- | ----------------------------------------------------------------------------------------- |
| Automation title | `Weekly README check`                                                                     |
| Prompt           | The instruction below                                                                     |
| Project          | Select the repository containing README.md; required                                      |
| Schedule         | Specific time → specific weekdays → Monday → 09:00                                        |
| Model            | Choose the provider/model that passed your manual run                                     |
| Session          | New chat each run for independent checks; Continue chat to retain the task's conversation |
| Use template     | Fills a starting title/prompt; review it before creating                                  |

```text
Read README.md in the selected project.
Report its main headings and local links whose targets are missing.
Include file references. Do not edit files or visit external websites.
```

Click **Create**. Session mode defaults to Continue chat in this dialog, so select New chat explicitly for this independent check.

## Set time without guessing

The schedule editor supports **Repeat interval**, **Specific time**, and raw **Cron**. Cron has five fields: minute, hour, day of month, month, weekday.

| Timing                 | Cron           |
| ---------------------- | -------------- |
| Every weekday at 09:00 | `0 9 * * 1-5`  |
| Monday at 09:00        | `0 9 * * 1`    |
| Every 30 minutes       | `*/30 * * * *` |

The desktop scheduler calculates local time on its host; the form has no independent timezone selector. Check the computer's timezone and the detail panel's **Next run**, especially after travel or a system-time change.

## Run once and inspect the result

Open the automation and click **Run Now**. In the detail sidebar, check **Status**, **Last ran**, **Total Runs**, and **Previous Runs**. Open that run's conversation and compare the reported headings/links with README.md.

A useful first result identifies the intended repository, contains checkable findings, and records failures explicitly. A successful manual run does not establish that the computer will be awake at the next scheduled time.

## Deliver results to the originating channel

A task created from a connected bot's channel conversation can inherit that channel as its notification target. After verifying the bot, mention it in the intended test group:

```text
Create a task named Weekly README check in this bot's project.
Every Monday at 09:00 on this computer, report README headings and broken local links.
Use a new conversation each run. Send the result back to this test group.
Show the schedule and destination after creation.
```

In Onevium, open the created automation and inspect **Notifications** for the bot, group, and enabled switch. Run it once and check the actual group message. The detail sidebar toggles existing targets; it is not a general “add any recipient” form. Desktop-created tasks do not automatically acquire a channel destination.

## Pause, resume, and change the task

Use **Pause** to prevent future triggers and **Resume** to enable them again. Pausing is not the same as stopping the current run: open its conversation to stop active work. Change the prompt, model, timing, or session mode in the detail controls and rerun a small check.

An already-running task can cause another trigger to be skipped. Continue chat can preserve context across runs, but that context may be compacted; put durable requirements in the prompt or project instructions.

## Common problems

- **No scheduled run:** check Pause, host timezone, Next run, sleep state, and whether Onevium was running.
- **Error in history:** open that run's conversation and fix the concrete provider, file, or tool failure.
- **Result exists but no group message:** inspect Notifications and its enabled switch, then check the bot connection and recipient.
- **Unexpected repetition:** check duplicate automations and whether you manually triggered an existing schedule.

## Next steps

Review [permissions](https://onevium.com/docs/permissions), [projects and sessions](https://onevium.com/docs/projects-and-sessions), or set up a [channel](https://onevium.com/docs/team-channels) before adding delivery.