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

# Schedules overview

> Run a published Canvas, Workflow or Agent by itself, on a recurring schedule or once

A **Schedule** starts a run for you at a time you choose. Instead of someone clicking **Run** or your system calling the API, Tela runs a published Canvas, Workflow or Agent every day, every Monday at 9:00, on the first of the month or once on a date you pick.

Use a schedule when the work follows the calendar and the inputs stay the same: a weekly report, a nightly check, a reminder run before a deadline. If the inputs change on every run, create [tasks in an App](https://docs.tela.com/en/workstation/workstation.md) or call the [Completion API](https://docs.tela.com/en/completion-api/overview.md) instead.

In this section the examples use the **Contract routing** Workflow from the [Workflow section](https://docs.tela.com/en/workflow/overview.md): a schedule that runs it every Monday at 09:00 with a contract and a requester saved on the schedule.

![Schedules page with a recurring schedule and a finished one-time schedule for the Contract routing Workflow](https://mintcdn.com/meistrari/M2w7BduKZAFA1Sbx/images/schedules/list.png?fit=max\&auto=format\&n=M2w7BduKZAFA1Sbx\&q=85\&s=25a8eafb6e1d93d233b24ed6d19f810e)

## What runs

A schedule never runs your work in progress. It runs what you published, and it looks up the version at the moment each run starts.

| Destination | Version that runs |
| - | - |
| Canvas | The version published to **Production** |
| Workflow | The version published to **Production** |
| Agent | The published version of the main branch |

This has a consequence worth remembering: publishing a new version changes what **every existing schedule** of that Canvas, Workflow or Agent runs next. A draft, an older version in the history or a version published only to another environment is never scheduled. A destination with no Production or published version does not appear in the list at all.

> [!TIP]
>
> Before you publish something that already has active schedules, check the **Schedules** page filtered by that destination. The next scheduled run will use the new version.

## Where to find schedules

* **Schedules** in the left sidebar lists every schedule of the Workspace and is where you create them.
* The `…` menu next to the title of a Canvas, Workflow or Agent has a **Schedule** option that opens the same form with the destination already chosen. When the destination is not published yet, the form asks you to publish first.

![The … menu of a Workflow with the Schedule option highlighted](https://mintcdn.com/meistrari/M2w7BduKZAFA1Sbx/images/schedules/workflow-menu.png?fit=max\&auto=format\&n=M2w7BduKZAFA1Sbx\&q=85\&s=0a0f5ad2e99dbb76c0ef1be53f3cc0d4)

## What a run looks like

Each time a schedule fires, Tela creates a normal run of the destination and records it in the schedule's **History**. You follow the result where you follow any other run:

* Canvas and Workflow: in **Usage**, with the source **Schedule**. A Workflow run also appears in **Debug**.
* Agent: as a session in **Usage**.

A schedule only decides **when a run starts**. There is no wait or delay inside a Canvas, Workflow or Agent. A process that has to wait hours or days for something external is built as two runs: one records what is pending and a recurring schedule starts another that picks up what is ready.

> [!NOTE]
>
> Every run spends credits like a run started by hand. A schedule that fires every minute is a lot of runs, so pick the slowest frequency that does the job.

## In this section

> **[Creating a schedule](https://docs.tela.com/en/schedules/creating-schedules.md)**
>
> Fields, frequencies, time zone, who can see it and the inputs of each run

> **[Managing schedules and history](https://docs.tela.com/en/schedules/managing-schedules.md)**
>
> Statuses, pausing, editing, deleting and what to do when a run fails


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