> 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/technical-reference/triggers-and-webhooks/schedules-time-zones-and-calendar-edge-cases.md).

# Schedules, Time Zones, and Calendar Edge Cases

Schedules start workflows at configured times. Choose an explicit time zone so the schedule matches the team’s operating hours.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FSvjrGkOKbO2ywKxIRNg8%2FG031.mp4?alt=media&token=2fdd194c-38a9-4ef6-9b09-f9a81df9001e>" %}

## Before you begin

Permission to configure and activate the schedule.

## Key concepts

| Term                 | Definition                                                                                                                                      |
| -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- |
| Daylight-saving time | A seasonal change to local clock offset in some time zones. Review local schedules around clock changes instead of assuming a fixed UTC offset. |
| Trigger              | A schedule or event source that starts a workflow. It must be configured and activated; discovering it in the catalog does not activate it.     |
| Activation           | The state in which a configured trigger can start work. Saving or listing a trigger does not establish that it is active.                       |

## Configuration options

| Option          | Purpose                                                                      | Behavior                                                                   |
| --------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------- |
| Time zone       | The geographic or fixed-offset time basis for a schedule.                    | Select it explicitly when a schedule must follow local working times.      |
| Cron expression | A structured expression describing a schedule on interfaces that support it. | Confirm it matches the human-readable schedule and the selected time zone. |

## Configure a schedule

1. Choose the frequency and time zone.
2. Set the days and times, then review the displayed schedule.

![Set the schedule’s frequency, time, and time zone in Configuration.](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/AMvzOhQaNrTS1AIhhRQC/assets/g031-g031-02-schedule-config.png)

Set the schedule’s frequency, time, and time zone in Configuration.

3. Activate the schedule and inspect the next run’s time and inputs.

Runs start according to the active schedule.

## Behavior and limitations

The default time zone is UTC where no other zone is selected. A monthly schedule for the 29th, 30th, or 31st can skip months without that date. Daylight-saving changes affect local clock times. Avoid overlapping schedules unless repeated execution is intentional, and use run history to confirm the actual start time.

## Related resources

[Triggers and scheduled and event runs](https://docs.stackai.com/guides-and-quickstarts/workflow-builder/triggers-and-scheduled-and-event-runs.md)

[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/technical-reference/triggers-and-webhooks/schedules-time-zones-and-calendar-edge-cases.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.
