> ## Documentation Index
> Fetch the complete documentation index at: https://docs.trusys.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Scheduled Jobs

Scheduled Jobs allow you to automatically run **Functional Evaluations** or **Security Evaluations** on a recurring basis. This helps continuously validate your AI applications against performance, reliability, and security requirements without manual intervention.

A Scheduled Job defines:

* **What** evaluation to run (Functional or Security)
* **Which application or configuration** to test
* **Which prompt library** to use for generating inputs
* **When and how often** the evaluation should run

Once created, the job runs automatically based on the defined schedule and stores results for later review.

***

# Creating a Scheduled Job

Navigate to **Scheduled Jobs** and click **Create Schedule**.\
Choose the type of evaluation you want to automate.

***

### Functional Evaluation Schedule

Use this option to run **TRU EVAL** functional tests on a recurring basis.

**Required Configuration**

* **Application**\
  Select the AI application you want to evaluate.

* **Prompt Library**\
  Select the prompt library that will be used to generate inputs for this evaluation.

* **Schedule Configuration**
  * **Start Date** – Date when the schedule becomes active
  * **Repeat Every** – Frequency of execution (e.g., every 2 days)
  * **Ends On**
    * **Never** – The schedule runs indefinitely
    * **After** – Ends after a fixed number of runs
    * **On Date** – Ends on a specific date

Once saved, Trusys will automatically execute the functional evaluation using the selected prompt library at the configured intervals.

***

### Security Evaluation Schedule

Use this option to run **TRU SCOUT** security and compliance evaluations on a recurring basis.

**Required Configuration**

* **Security Configuration**\
  Select an existing security configuration (validators, policies, thresholds).

* **Prompt Library**\
  Select the prompt library that will be used to generate inputs for this security test.

* **Schedule Configuration**
  * **Start Date** – Date when the first evaluation run begins
  * **Repeat Every** – Frequency of execution (e.g., every 2 days)
  * **Ends On**
    * **Never** – The schedule runs continuously
    * **After** – Ends after a defined number of executions
    * **On Date** – Ends on a specific date

***

# View and Manage Scheduled Jobs

The **Scheduled Jobs** page provides a centralized view of all schedules created in your project.\
For each scheduled job, you can see:

* Evaluation type (Functional or Security)
* Associated application or security configuration
* Status (Active / Paused / Completed)
* TOtal test runs complete

***

### Scheduled Job Details

Clicking on a scheduled job opens the **Scheduled Job Details** view.

From here, you can:

**View Evaluation Runs**

* See a chronological list of all evaluations triggered by the schedule
* Open individual evaluation results to review functional metrics, security findings, and violations
* Track trends across repeated runs over time

***

### Edit Schedule Configuration

You can update:

* Start date or end conditions
* Execution frequency

Changes apply to **future runs only** and do not affect completed evaluations.

**Archive a Schedule**
Archived schedules:

* Are removed from active execution
* Remain available for historical reference and audit purposes
* Cannot be edited or resumed once archived