> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/built-in-triggers/scheduled-execution.md).

# Scheduled Execution

Start a workflow automatically at chosen times. Use it for recurring work that does not need a person to submit an input for each run.

## Before you start

You need permission to configure and publish the workflow. Its connections and required resources must be available for unattended execution.

## Schedule a workflow

1. Add the **Scheduled Execution** trigger and connect it to the steps that should run.
2. Choose **Frequency**, the relevant day fields, **Time(s)**, and **Timezone**. Check that the workflow has the information it needs without a chat message.
3. Publish the workflow to activate the trigger. If your organization requires release approval, complete that process.
4. After the scheduled time, inspect run history and verify the output or destination.

**Result:** The active schedule starts the published workflow at the configured times.

## Behavior and troubleshooting

Saving a configuration alone does not activate the schedule. Multiple times must use the same minute value. Days 29, 30, and 31 are skipped in months that lack the selected date. Check timezone and calendar behavior before scheduling time-sensitive work. See [Schedules, Time Zones, and Calendar Edge Cases](https://docs.stackai.com/technical-reference/triggers-and-webhooks/schedules-time-zones-and-calendar-edge-cases.md).

**Configuration**

<table><thead><tr><th width="220">Parameter</th><th width="160">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>Frequency</code> *</td><td>dropdown (string)</td><td>How often the scheduled execution should run. Choose one of: Every day, Every week, Every month, Custom. Default: <code>every_day</code>.</td></tr><tr><td><code>Day of the week</code></td><td>dropdown (string)</td><td>Day of the week when the scheduled execution should run (for weekly frequency). Choose one of: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. Only shown when Frequency is Every week.</td></tr><tr><td><code>Days of the week</code></td><td>multi-select (string)</td><td>Days of the week when the scheduled execution should run (for custom frequency). Choose any of: Monday, Tuesday, Wednesday, Thursday, Friday, Saturday, Sunday. Only shown when Frequency is Custom.</td></tr><tr><td><code>Day of the month</code></td><td>dropdown (string)</td><td>Day of the month when the scheduled execution should run (for monthly frequency). Days 29, 30, and 31 are skipped in months that don't have those days. Choose one of: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31. Only shown when Frequency is Every month.</td></tr><tr><td><code>Time(s)</code> *</td><td>array</td><td>Times of the day when the scheduled execution should run (format: HH:MM, e.g., 8:00, 12:00). You can add multiple times, but all times must have the same minute value (e.g., 8:00, 12:00, 15:00 - all at :00). Default: <code>['9:00']</code>.</td></tr><tr><td><code>Timezone</code> *</td><td>dropdown (string)</td><td>Timezone for the scheduled execution. Choose one of: PACIFIC TIME, MOUNTAIN TIME, CENTRAL TIME, EASTERN TIME, ATLANTIC TIME, UTC, LONDON, PARIS, BERLIN, MOSCOW, DUBAI, INDIA, SINGAPORE, TOKYO, SYDNEY, AUCKLAND. Default: <code>UTC</code>.</td></tr></tbody></table>

## Related guidance

[Trigger Activation and Execution Context](https://docs.stackai.com/technical-reference/triggers-and-webhooks/trigger-activation-and-execution-context.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/built-in-triggers/scheduled-execution.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
