# Schedule Trigger

### Overview

The Schedule Trigger (**Scheduler**) allows you to execute workflows automatically based on time. Instead of triggering actions manually, you can schedule workflows to run **once at a specific time** or **repeatedly at fixed intervals**.

This is ideal for automation use cases such as recurring on-chain actions, periodic data fetches, routine fund transfers, or timed smart contract interactions.

***

### What the Scheduler Does

The Scheduler acts as a **time-based trigger** that starts your workflow execution according to predefined rules. Once configured, it runs independently without manual intervention.

Key capabilities include:

* Delayed execution (run after a set duration)
* One-time scheduled runs
* Recurring executions at regular intervals
* Minute, hour, or day-level granularity

***

### Configuration Options

#### 1. Schedule Type

Choose how you want to define the execution time:

* **Schedule In**\
  Runs the workflow after a specified duration (e.g., after 10 minutes).
* **Schedule At**\
  Runs the workflow at an exact date and time.

***

#### 2. When to Run

Defines whether the workflow executes once or repeatedly:

* **Run Once**\
  Executes the workflow a single time based on the schedule.
* **Repeat Every**\
  Executes the workflow repeatedly at the defined interval.

***

#### 3. Run In (Value)

Specifies the numeric duration before execution (used with **Schedule In**).

Example:

* Value: <mark style="color:$primary;">10</mark>
* Unit: <mark style="color:$primary;">Minutes</mark>
* Result: Workflow runs after 10 minutes

***

#### 4. Unit

Defines the time unit for scheduling:

* Minutes
* Hours
* Days

***

#### 5. Schedule Preview

Displays a human-readable summary of when the workflow will run.\
This helps verify your configuration before activating the schedule.

Example:

> **Run once in 10 minutes**

***

### Common Use Cases

* **Recurring blockchain monitoring**
* **Delayed smart contract execution**
* **Automated periodic fund transfers**
* **Scheduled data reads or API calls**
* **Time-based notifications or alerts**

***

### Example Workflow

**Scenario:** Run a workflow every 10 minutes to fetch on-chain data.

* Schedule Type: `Schedule In`
* When to Run: `Repeat Every`
* Run In: `10`
* Unit: `Minutes`

Result: The workflow executes automatically every 10 minutes.

***

###


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.decimal.at/technical/node-directory/schedule-trigger.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.