# Scheduled tasks

Scheduled tasks let Adam run saved instructions once in the future or on a repeating schedule.

## Create a schedule

**Open Scheduled**
Select **Scheduled** in the sidebar, then select **New scheduled task**.
**Describe the work**
Enter the instructions Adam should follow each time. You can also give the task a name.
**Choose when it runs**
Select a one-time date, hourly, daily, weekly, monthly, or custom schedule. Check the time zone shown before saving.
**Create and review**
Save the task. Open it later to see previous runs, change its instructions, or adjust the schedule.

## Manage a scheduled task

From **Scheduled**, you can search your scheduled tasks and use the action menu to:

- edit the name, instructions, or schedule;
- pause or resume future runs;
- review previous runs; or
- delete the automation.

Pausing keeps the task but stops future runs until you resume it.

For work in a desktop application, keep the schedule owner's paired workstation, connector, application, and required license available at run time. A schedule does not turn on an offline computer. Test the instructions once on a representative input before scheduling a batch or an edit.

## Event-triggered work

Adam can also create tasks that run after supported events in a connected product. Tell Adam what event should start the task and what it should do.

You can edit the task's name and instructions from **Scheduled**. To change the event that starts it, ask Adam to update or recreate the task.

Scheduled tasks can run while you are away. Be clear about what Adam may change. For sensitive work, ask it to report what it finds without making changes.

## Write reliable instructions

Include:

- what Adam should review;
- the time window to inspect;
- the expected output and destination;
- what counts as an exception; and
- whether Adam may make changes or should only report what it finds.

```text
Every Monday at 9:00 AM, search for engineering news about injection molding materials published during the previous seven days. Summarize the five most relevant updates, include a link to each source, and explain why each update matters to a product design team.
```