# Create your first schedule

> Create a schedule that syncs data from your devices automatically, at the days and interval you choose.

Section: Getting Started  
Source: https://www.itva.com/docs/getting-started/create-your-first-schedule  
Last updated: 2026-11-02

In this guide, you create a schedule that syncs your devices automatically, and you confirm that it runs.

A schedule runs one or more jobs at a set interval. A device job runs the same tasks as a manual sync, on the devices that you select.

## Before you begin

- You have added at least one device.
- A manual sync of that device succeeded. See [Sync data from your devices](https://www.itva.com/docs/getting-started/sync-data-from-your-devices). If a manual sync fails, a scheduled sync of the same device also fails.

## Create the schedule

1. In the portal, go to **Inventory > Schedules**.
2. Select **New Schedule**.
3. Enter a **Name** for the schedule.
4. In **Day(s)**, select the days to run the schedule. All days are selected by default.
5. In **Interval**, select how often to run the schedule: **Daily**, or every 2m, 5m, 10m, 15m, 30m, 1h, 2h, 4h, or 8h.
6. If the interval is **Daily**, set the **Time**. The default is 00:00.
7. Select the **Timezone**.

## Add a job

Each schedule has one or more jobs. The form starts with **Job #1**.

1. In **Kind**, select **Device**.
2. In **Task(s)**, select the tasks to run, for example **Sync Interfaces** and **Run Health Check**.
3. Select the devices for the job. To include a group of devices, select one or more tags.
4. To run different tasks on other devices, select **+ Job** and repeat these steps.
5. Select **Save**.

## Check that it worked

1. Go to **Inventory > Schedules** and open the schedule.
2. Make sure **Enabled** is on.
3. To test the schedule now, select **Run**.
4. Open one of the devices in the job and go to its **Schedules** tab. Make sure the jobs and tasks show there.

## Troubleshooting

If the schedule runs but a device has no new data, do a manual sync of that device and read the log. The log shows which task failed and why.
