---
title: "Studio Jobs and Job Orchestration"
slug: "studio-jobs-and-job-orchestration"
description: "Explains what jobs in RapidIdentity Studio do, how they're scheduled and how they run"
tags: ["Administrator", "Studio", "Rostering", "OneRoster", "RapidIdentity Connect"]
updated: 2024-04-02T17:27:55Z
published: 2024-04-02T17:27:55Z
canonical: "help.rapididentity.com/studio-jobs-and-job-orchestration"
---

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

# Studio Jobs and Job Orchestration

## Studio Jobs and Job Orchestration

Rostering with RapidIdentity Studio is a three-step process involving the use of *Jobs* that automatically execute the various tasks of extracting rostering data from source systems, transforming that data into Studio and making that data ready to be loaded into the associated rostered target applications.

![](https://cdn.document360.io/4d958006-b877-42af-8de5-00e3bb7fe41d/Images/Documentation/image(538).png)

#### Studio Jobs

1. Data from source systems is read into Source Tables in Studio, one for each source system. No data transformations are performed in this step; however, each application record associated with each source system can be configured with `Record Filters `to restrict the data consumed based on specific field values. *Each Source Application installed in Studio has a corresponding Studio Job that performs this task.*
2. Data from the Source Tables in Studio is transformed and mapped into the Main Table in Studio. Data mappings are performed based on pre-defined instructions, `mapping expressions`, for each of the records in each of the source applications. These expressions define how data from the source system is transformed and mapped into Studio. *There are several Studio Jobs that perform these tasks.*
3. Data from the main table in Studio is transformed and mapped into target tables in Studio, one for each target system. Studio `Access Groups `and or `Record Filters `can be configured for each target application to filter the data sent from Studio to the target application. *There are several Studio Jobs for each of the target systems that perform these tasks.*

#### Job Orchestration

Studio *Jobs* are scheduled to run in an orchestrated manner. Once the schedule has been set, all `enabled `jobs in Studio will be run in the following stages:

1. Source system jobs run first and are automatically started based on the job schedule
2. Studio jobs run after source system jobs have completed
3. Target application jobs run after the studio jobs have completed

*All enabled jobs in each stage run automatically and in parallel. Jobs that are not enabled must be run manually.*

## Related

- [Mappings, Matching and Event Governance](/mappings-matching-and-event-governance.md)
- [Studio Mapping Expressions](/studio-mapping-expressions.md)
- [Studio Access Groups](/studio-access-groups.md)
- [Studio](/rostering-with-rapididentity-studio.md)
- [Studio Job Scheduling Update in RapidIdentity 2022.4.5](/studio-scheduling-update.md)
- [Studio Troubleshooting Best Practices](/studio-best-practices.md)
- [Studio Updates Webinar](/studio-updates-webinar.md)
- [Studio Overview Webinar](/studio-overview.md)
- [Common Studio Log Error Definitions](/common-studio-log-error-definitions.md)