---
title: "Scheduler.Schedule"
slug: "schedulerschedule"
tags: ["luminesce ", "provider", "scheduler", "schedule"]
updated: 2024-08-21T13:25:33Z
published: 2024-08-21T13:25:33Z
canonical: "support.lusid.com/schedulerschedule"
---

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

# Scheduler.Schedule

| **Type** | **Read/write** | **Author** | **Availability** |
| --- | --- | --- | --- |
| [Data provider](/v1/docs/what-are-a-data-provider-and-a-direct-provider) | Read | Finbourne | Provided with LUSID |

The `Scheduler.Schedule` provider enables you to write a [Luminesce SQL query](/v1/docs/understanding-the-luminesce-sql-query-syntax) that retrieves schedule data from [Scheduler](/v1/docs/scheduler).

> **Note:** The LUSID user running the query must have sufficient [access control permissions](/v1/docs/creating-policies-to-control-access-to-providers-for-different-luminesce-end-users) to both use the provider *and* read Scheduler schedule data. This should automatically be the case if you are the domain owner.

**See also:** [Scheduler.Job](/v1/docs/schedulerjob), [Scheduler.Schedule.Run](/v1/docs/schedulerschedulerun)

## Basic usage

```sql
select * from Scheduler.Schedule where <filter-expression>;
```

## Query parameters

`Scheduler.Schedule` has parameters that enable you to filter or refine a query.

To list available parameters, their data types, default values, and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, ParamDefaultValue, Description from Sys.Field where TableName = 'Scheduler.Schedule' and FieldType = 'Parameter';
```

## Data fields

By default, `Scheduler.Schedule` returns a table of data populated with particular fields (columns). You can return a subset of these fields.

To list fields available to return, their data types, whether fields are considered 'main', and an explanation for each, run the following query using a [suitable tool](/v1/docs/what-tools-are-available-to-write-luminesce-queries):

```sql
select FieldName, DataType, IsMain, IsPrimaryKey, SampleValues, Description from Sys.Field where TableName = 'Scheduler.Schedule' and FieldType = 'Column';
```

> **Note:** Fields marked 'main' are returned by queries that include a caret character, for example `select ^ from Scheduler.Schedule`.

## Examples

> **Note:** For more example Luminesce SQL queries, visit our [Github repo](https://github.com/finbourne/luminesce-examples/tree/master/examples).

### Example 1: Retrieve first ten schedules

```sql
select * from Scheduler.Schedule limit 10
```

### Example 2: Retrieve all schedules that exist for a particular job

```sql
select * from Scheduler.Schedule where JobScope = 'transactions' and JobCode = 'upsert-transactions'
```

### Example 3: Retrieve trigger information and the arguments a schedule is configured to run with

```sql
select Trigger, Arguments from Scheduler.Schedule where ScheduleScope = 'transactions' and ScheduleCode = 'upsert-transactions-schedule'
```

### Example 4: Retrieve all schedules created by a particular person

```sql
select * from Scheduler.Schedule where Author = 'Joe Bloggs'
```

### Example 5: Retrieve schedule run history for a particular schedule name

```sql
select * 
from Scheduler.Schedule s
join Scheduler.Job.History h
  on s.ScheduleScope = h.ScheduleScope
  and s.ScheduleCode = h.ScheduleCode
where s.Name = 'Automate upsert transactions'
```