> ## Documentation Index
> Fetch the complete documentation index at: https://docs.oviond.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduled delivery

> Set the frequency, day, and time an automation sends.

Each automation sends its report on a recurring schedule you define. Oviond renders the report for the configured date range and emails it to your recipients — no manual sending required.

## Set the schedule

When you create or edit an automation, the **Schedule** step controls when it sends:

* **Frequency** — **Daily**, **Weekly**, or **Monthly**.
* **Day of week** — shown for **weekly** automations (Monday–Sunday).
* **Day of month** — shown for **monthly** automations (day `1`–`31`).
* **Send at** — the hour, minute (`00` or `30`), and `AM`/`PM`.

The schedule is stored as `frequency`, `day`, `hours`, `minutes`, and `time_format`, and is evaluated against the account's `timezone`. The send time is shown in that timezone in the automation's details.

<Note>
  Oviond checks for due automations every minute, so a run starts shortly after its scheduled time rather than exactly on the second.
</Note>

## Date range

The **Date range** (for example `Last Month`) is stored as `date_text` and decides which period the report covers. It's resolved fresh on every run, so a monthly automation set to `Last Month` always sends the most recent complete month.

## After it's scheduled

Once saved, the automation runs on its next scheduled time. From the **Automations** screen you can:

* **Edit** the schedule, recipients, template, or sender at any time. Changing the schedule recomputes the next run.
* **Pause / Resume** to suspend sending without losing the configuration.
* **Test** to send immediately — see [Test an automation](/automations/test).
* **Archive** to stop and remove it — see [Archive an automation](/automations/delete).

## View execution history

Open an automation and click **Executions** (or open the project's run history) to see every past run — scheduled and test — with its timestamp and status. See [Run history](/automations/history).