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

# Creating a Task Schedule

> Set up one task schedule: flow, starting values, assignee, repeat cycle and active period.

> [!NOTE]
>
> Required permission:
>
> * View schedule
> * Create schedule

There are two ways to create task schedules:

* Click **New** to create one schedule, as described on this page.
* Click the arrow beside **New** and choose **Bulk** to create many at once from a spreadsheet. See [Bulk Create Task Schedules](https://docsy3.mile.app/pages/planning/schedule/bulk-create-task-schedules.md).

![New and Bulk](https://mintcdn.com/mile-app/WPibWyW63U4l5gcF/images/v4/planning/schedule/task-new-menu.png?fit=max\&auto=format\&n=WPibWyW63U4l5gcF\&q=85\&s=06fb5a3bfe2bc3b8037899415cc9a3ac)

1. **Bulk**: create many schedules from a spreadsheet.

## The New task schedule form

Click **New**. Pick a **Flow** first: the fields of that flow's initial page appear in the form.

![New task schedule](https://mintcdn.com/mile-app/WPibWyW63U4l5gcF/images/v4/planning/schedule/task-new.png?fit=max\&auto=format\&n=WPibWyW63U4l5gcF\&q=85\&s=ca7fdbe6cb702e3c9979a8adc955d003)

1. **Name**: a name that tells this schedule apart from your other schedules, for example "Daily Store Restock".
2. **Flow**: the flow every run creates a task from, for example Pickup or Delivery. Every run creates one task.
3. **What each task starts with**: the fields of the flow's initial page. What you fill in here is copied into every task the schedule creates, for example the customer, address and order items. Fields left empty stay empty on each task. Data source fields let you search and pick a record, and coordinates are found from the address when you leave them empty. If the flow has its initial page turned off, the form says so and the tasks start empty.
4. **Repeat**: how often the schedule creates a task. See [Repeat cycles](#repeat-cycles) below.
5. **Times of day**: the time the task is created. Click **Add a time** to add more times. Times are entered in your own time zone (the form shows it, for example UTC+7 Asia/Jakarta) and stored in UTC.
6. **Active from / Active until**: the period in which the schedule runs. Before **Active from** and after **Active until**, no tasks are created. The end has to be at least a day after the start.
7. **Create task schedule**: save the schedule. The message "Task schedule created." confirms it.

## Assignee

Scroll down to the **Assignee** field, below the flow fields.

![Assignee](https://mintcdn.com/mile-app/WPibWyW63U4l5gcF/images/v4/planning/schedule/task-new-assignee.png?fit=max\&auto=format\&n=WPibWyW63U4l5gcF\&q=85\&s=452585c2e23b578fa3a6c307317c7da0)

1. **Assignee**: who each created task is assigned to. Pick one or more people from the **User** and **Team** sections. The list comes from the hub selected at the top of the page. Leave it on **Nobody yet** to create unassigned tasks.

If a required field is missing, the form stays open and shows what is needed, for example "Give the schedule a name." or "Pick the flow to create tasks from." If you close the form after filling it in, you're asked whether to discard the details.

## Repeat cycles

| Repeat | Details |
| - | - |
| **Every day** | [Repeat daily](https://docsy3.mile.app/pages/planning/schedule/repeat-cycle/daily.md) |
| **Every week** | [Repeat weekly](https://docsy3.mile.app/pages/planning/schedule/repeat-cycle/weekly.md) |
| **Every month** | [Repeat monthly](https://docsy3.mile.app/pages/planning/schedule/repeat-cycle/monthly.md) |
| **On fixed dates** | [Repeat on fixed dates](https://docsy3.mile.app/pages/planning/schedule/repeat-cycle/by-date.md) |
| **Custom cycle** | [Custom cycle](https://docsy3.mile.app/pages/planning/schedule/repeat-cycle/custom.md) |

![Repeat options](https://mintcdn.com/mile-app/WPibWyW63U4l5gcF/images/v4/planning/schedule/repeat-options.png?fit=max\&auto=format\&n=WPibWyW63U4l5gcF\&q=85\&s=44e6e3034279040c0a8b622719959a6b)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.