---
title: "Scheduler"
slug: "scheduler"
tags: ["job scheduler", "automation"]
updated: 2024-09-26T13:06:58Z
published: 2024-09-26T13:06:58Z
canonical: "support.lusid.com/scheduler"
---

> ## 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

Scheduler is a job automation tool built in to LUSID.

You can write code to perform any operation, for example upserting transactions into LUSID from a trade file. You can then create a *job* in LUSID by uploading a Docker image containing that code, and subsequently *schedule* that job to run automatically.

The LUSID ecosystem consists of [multiple applications](/v1/docs/understanding-all-the-applications-in-the-finbourne-platform), each with their own API. The code in your job can call any endpoint in either the core LUSID or the Identity or Access APIs. (Alternatively, your job could perform a non-LUSID operation.)

Providing you have appropriate [access control permissions](/v1/docs/setting-up-access-control-for-different-scheduler-users), you can interact with Scheduler using the [LUSID web app](https://www.lusid.com/app/home), via the **Jobs & Scheduling** menu:

![](https://cdn.document360.io/d575ad81-c0ed-4980-bbd1-d59ac5c3de82/Images/Documentation/ae30aa4f-445a-4f1e-b82d-b29130859d4d.png)

Alternatively, you can interact with Scheduler programmatically:

- Using the [Scheduler REST API](https://www.lusid.com/docs/api/scheduler/intro)
- Using the [Scheduler SDK](/v1/docs/understanding-all-the-applications-in-the-finbourne-platform) in various languages
- If you have a Luminesce license, using dedicated [read and write providers](/v1/docs/readwrite-to-scheduler-scheduler).

**Tutorials**: *Get started by doing something tangible*

- [Automatically upserting transactions into LUSID from a CSV file](/v1/docs/automatically-upserting-transactions-into-lusid-from-a-csv-file)
- [Setting up access control for different Scheduler users](/v1/docs/setting-up-access-control-for-different-scheduler-users)

**Reference**: *Understand concepts and implications*

- [Storing secrets and parameters in the Configuration Store](/v1/docs/storing-secrets-and-parameters-in-the-configuration-store)
- [Troubleshooting Docker image vulnerabilities](/v1/docs/troubleshooting-docker-image-vulnerabilities)
- [Monitoring job run history and troubleshooting failures](/v1/docs/monitoring-job-run-history-and-troubleshooting-failures)
- [Access control for Scheduler resources](/v1/docs/access-control-for-scheduler-resources)
- [Using Luminesce providers to interact with Scheduler](/v1/docs/using-luminesce-to-readwrite-to-the-scheduler)

**How-to guides**: *Get something done*

- [How do I upload a Docker image to the FINBOURNE AWS store?](/v1/docs/how-do-i-upload-a-docker-image-to-the-finbourne-aws-store)
- [How do I create a job?](/v1/docs/how-do-i-create-a-job)
- [How do I create a schedule to automate job runs?](/v1/docs/how-do-i-create-a-schedule-to-automate-job-runs)
- [How do I schedule a Luminesce SQL query?](/v1/docs/how-do-i-schedule-a-luminesce-sql-query)
- How do I create an image?