# Scheduling Recipes

## Overview

Karini AI supports scheduling recipes, allowing for the automated execution of workflows at specified times or intervals. This functionality ensures tasks are carried out according to predefined schedules, minimizing manual intervention and ensuring reliable, timely execution. With flexible scheduling options, users can configure precise start times, set repeat intervals, and define durations, enabling the automation of both one-time and recurring tasks. This capability optimizes operational efficiency and ensures consistent workflow execution across a wide range of scenarios.

## Scheduling in workflow recipes

**Workflow Recipes** can be scheduled to run automatically using a **Webhook node**. The Webhook node acts as a trigger, executing the recipe at a specified time, interval, or upon receiving an external request. This scheduling feature supports both **recurring** and **one-time** runs, providing flexibility for a wide range of operational needs.

### Steps to Schedule an Workflow Recipe

#### 1. Configure the Connector Node

Set up the connector node with the required parameters:

* **S3 Bucket Path**: Enter the full path of  the Amazon S3 bucket that contains the files to be processed.
  * *Example*: `s3://my-bucket/files/`
* **S3 Prefix**: Define a subfolder within the bucket to filter files for processing.
  * *Example*: `2025/september/`

Once configuration is complete, save your changes, publish the recipe, and deploy it for use.

#### 2. Open the Scheduling Menu

1. Click the **Action** button in the top-right corner.
2. Select **Schedule** from the dropdown menu.

#### 3. Define Scheduling Details

Fill in the following scheduling information:

* **Schedule Date/Time**
  * **Date**: Select the start date for the recipe run.
  * **Time**: Specify the exact time for execution.
* **End Date/Time (Optional)**
  * Define an end date and time if you want the schedule to stop automatically.
* **Repeat Settings**
  * Enable the **Repeat** option to create a recurring schedule.
  * **Frequency**: Set how often the recipe should repeat (e.g., every 1 day, every 2 weeks).
  * **Period**: Choose one of the following recurrence intervals:
    * Hours
    * Days
    * Weeks
    * Months
* **Input Message (Optional)**
  * Add a message or note for reference or logging purposes.

#### 4. Choose an Action

* **Schedule Recipe Run** – Save and activate the schedule.
* **Remove Schedule** – Delete the existing schedule configuration.
* **Cancel** – Exit without saving changes.

#### 5. Review Scheduled Recipes

Once scheduling is complete and the recipe is scheduled, the status will be added to the **Recipe Table**. The recipe table provides a consolidated overview of all active and upcoming scheduled tasks.

## Scheduling QnA and Graph Recipes

In addition to Agent Recipes, the **Scheduling Recipes** feature is also available for **Knowledgebase Recipes** and **Graph Recipes**. This capability enables automated document processing at predefined times or intervals, eliminating the need for manual execution.

When a schedule is configured, the recipe automatically processes documents from the connected data sources (connectors). This ensures that the latest content is continuously ingested, indexed, and ready for use in queries or graph-based operations.

To schedule QnA or Graph Recipes, simply follow the same [scheduling ](#id-2.-open-the-scheduling-menu)steps as for Agent Recipes. 

> Connector node configuration is not required.


---

# 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://karini-ai.gitbook.io/karini-ai-documentation/scheduling-recipes.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.