> For the complete documentation index, see [llms.txt](https://karini-ai.gitbook.io/karini-ai-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://karini-ai.gitbook.io/karini-ai-documentation/scheduling-recipes.md).

# Scheduling Recipes

### Overview

Karini AI supports recipe scheduling, allowing recipes to execute automatically at specified dates, times, or recurring intervals. This functionality ensures that tasks are performed according to predefined schedules, minimizing manual intervention and supporting reliable, timely execution.

Flexible scheduling options allow users to define precise start times, configure repeat intervals, and specify the period during which a schedule remains active. Recipes can be configured for one-time or recurring execution, helping organizations automate workflow operations, document ingestion, indexing, and graph-processing activities across a wide range of use cases.

Scheduling is available for all supported recipe types:

* **Workflow Recipes** execute configured workflow logic automatically.
* **Knowledge Base Recipes** process and index documents from their configured data sources.
* **Graph RAG Recipes** process content and update graph data used for graph-based retrieval.

#### Scheduling Workflow Recipes

A Workflow Recipe can be scheduled when a **Webhook node** is configured as its trigger. The recipe may also include Agent, Prompt, Connector, Processing, Router, or other supported nodes, depending on the workflow design.

Webhook-based Workflow Recipes support both **single scheduling** and **multiple scheduling**, allowing users to configure either one schedule or several independent schedules for the same recipe.

When a Connector node is used, complete its connection and data-source configuration before scheduling the recipe. The required settings vary by connector. Examples include:

* **Amazon S3 Connector**
  * **S3 Bucket Path:** Enter the complete path of the bucket containing the files to process, such as `s3://my-bucket/files/`.
  * **S3 Prefix:** Enter an optional folder or object prefix to restrict processing to a specific location, such as `2025/september/`.
* **Email Connector**
  * Configure the connector to retrieve emails received from your configured email IMAP inbox
  * Verify that the required mailbox connection, authentication, and email-filter settings are configured correctly before scheduling the recipe.

After completing the required configuration, save, publish, and deploy the recipe.

#### Scheduling Knowledge Base and Graph RAG Recipes

Knowledge Base and Graph RAG Recipes can be scheduled to process content automatically at predefined dates, times, or intervals using their existing configured data sources. Connector node configuration is not required during scheduling because both recipe types use the data sources already associated with their configurations.

Each Knowledge Base or Graph RAG Recipe supports **a single schedule**.

Scheduled execution supports the following operations:

* **Knowledge Base Recipes:** Retrieve and process new or updated documents, generate embeddings, update indexes, and make current content available.
* **Graph RAG Recipes:** Perform document ingestion, content extraction, entity and relationship identification, graph construction, and graph updates.

This capability keeps indexed and graph-based content current without requiring users to run the recipes manually.

#### Configuring a Recipe Schedule

Follow these steps to configure and activate a recipe schedule:

1. **Open the recipe**
   * Navigate to the required Workflow, Knowledge Base, or Graph RAG Recipe.
   * Confirm that the recipe configuration is complete.
   * For Workflow Recipes, ensure the recipe is saved, published, and deployed before scheduling.
2. **Open the Recipe Schedules panel**

   * Select **Actions > Schedule**.

   <figure><img src="https://415930246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZrVuiAUMyuYVvrK5KaB%2Fuploads%2Fo6zJLln4wYarbLnDbch7%2Fimage.png?alt=media&amp;token=155bf77f-1c2f-439b-bba6-a2f10f7f8fff" alt=""><figcaption></figcaption></figure>

   * The **Recipe Schedules** panel displays all active and upcoming schedules associated with the recipe.

   <figure><img src="https://415930246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZrVuiAUMyuYVvrK5KaB%2Fuploads%2FQx0adSnmiSMegeBzYahD%2Fimage.png?alt=media&amp;token=02ebd9c3-92c7-404c-989f-096895d70b0b" alt=""><figcaption></figcaption></figure>
3. **Add a schedule**

   * Select **Add Schedule**.
   * The schedule configuration form opens.

   <figure><img src="https://415930246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZrVuiAUMyuYVvrK5KaB%2Fuploads%2FuapTY14P41X91VjJtAZQ%2Fimage.png?alt=media&amp;token=4fb0708e-3366-4cd6-9b84-269908eb4b9c" alt=""><figcaption></figcaption></figure>

   * For recipe types that support multiple scheduling, repeat this process to add additional independent schedules.
4. **Enter the schedule details**
   * **Schedule Name:** Enter a unique and descriptive name for the schedule.
   * **Schedule Date and Time:** Select the date and time for the first execution. The selected value must be in the future.
   * **End Date and Time:** Specify when the scheduling period should end. The end date and time must be later than the schedule start date and time.
   * Schedule times are interpreted according to the local browser time zone.
5. **Select the scheduling method**

   * **One-time schedule:** Leave **Repeat** and **Cron** disabled. The recipe runs once at the specified date and time.
   * **Recurring schedule:** Enable **Repeat**, enter the required frequency, and select **Hours**, **Days**, **Weeks**, or **Months** as the recurrence period.
   *

   ```
   <figure><img src="/files/GuPrG7Yy49TEtqWJJr1v" alt=""><figcaption></figcaption></figure>
   ```

   * **Cron schedule:** Where supported, enable **Cron** and configure the Minutes, Hours, Day of month, Month, Day of the week, and Year fields.
   * &#x20;**Repeat** and **Cron** cannot be enabled simultaneously.
   *

   ```
   <figure><img src="/files/GPf2VN2kQXJX1F9o76qu" alt=""><figcaption></figcaption></figure>
   ```
6. **Provide an Input Message, where applicable**
   * Enter the instructions or execution context that should be passed to the recipe when the schedule is triggered.
   * For Workflow Recipes, the message can provide instructions to an Agent or Prompt node.
   * When **multiple schedules** are configured, each schedule can use a different Input Message.
7. **Save and activate the schedule**
   * Select **Schedule Recipe Run** to save and activate the schedule.
   * Select **Cancel** to close the form without saving.
   * After activation, the schedule appears in the **Recipe Schedules** panel with its next execution time, recurrence, end date, and status.
8. **Review the configured schedule**
   * Verify that the displayed date, time, recurrence, and end date are correct.
   * Use the **Edit** action to update the configuration.
   * Use the **Delete** action to remove the schedule and stop its future executions.

When a one-time schedule completes or a recurring schedule reaches its configured End Date and Time, it stops triggering the recipe and is automatically removed from the **Recipe Schedules** list. Other active schedules associated with the recipe continue to run independently.

#### **Viewing Schedule Information**

Select the **Schedule** icon to review the recipe’s upcoming execution details. The **Schedule Information** dialog displays the next scheduled run date and time, along with the configured recurrence interval.

<figure><img src="https://415930246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZrVuiAUMyuYVvrK5KaB%2Fuploads%2Fg3e8b8wJZZqniJrPF734%2Fimage.png?alt=media&amp;token=f5dc964b-edca-427a-a14a-2c86fe744264" alt=""><figcaption></figcaption></figure>

#### Viewing Scheduled Runs in the Recipes List

The **Scheduled** column displays the next scheduled execution date and time for each recipe, together with its recurrence frequency when applicable. This allows users to review upcoming scheduled runs directly from the **Recipes** list.

<figure><img src="https://415930246-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZrVuiAUMyuYVvrK5KaB%2Fuploads%2FNNdeVpFrGu1iuL50VdAa%2Fimage.png?alt=media&amp;token=4c9c04cd-9cd1-4570-83d3-d892c2e1fb68" alt=""><figcaption></figcaption></figure>

<br>