---
title: "Allowing a Job to Specify Thread Pool"
slug: "allowing-a-job-to-specify-which-thread-pool-to-run-in"
description: "This document shows users how to configure the Queue Name feature under Job Queues, to specify which Thread Pool a scheduled job goes to within a setup Ad Sync Job.  This allows users the ability to designate the order that their scheduled jobs occur in. "
updated: 2024-07-03T18:55:04Z
published: 2024-07-03T18:55:04Z
canonical: "documentation.decisions.com/allowing-a-job-to-specify-which-thread-pool-to-run-in"
---

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

# Allowing a Job to Specify Thread Pool

## Overview

By default, the Job Scheduler runs all jobs in the same Queue; this means that only one job will run at a time. For example, if Job A is scheduled to run at 5:00 PM and Job B is scheduled to run at 5:10 PM, but Job A takes 20 minutes to complete, Job B will not begin running until 5:20 AM because it could not start until Job A had completed. The Job Scheduler protects the server from being inundated by too many jobs running at once. However, in some cases, a user may want to override this default behavior and allow a job to run in a separate Job Queue, thus allowing it to run in parallel with other jobs.

---

## **Example**

There are many different jobs, but all have the same option for configuring **Queue Name**. This setting is the same regardless of job type, and this example will show how to change the **Queue Name** option on the **Job Settings** Page. Create five jobs to fully illustrate how to use **Job Queues** and configure their **Queue names**.

1. Navigate to the **System > Jobs and Events > Scheduled** **Jobs** Folder in the Portal. Then, click **NEW AD SYNC JOB** from the top Action bar.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-06-20_14h59_42.png)
2. Create an **Ad Sync Job** with the **Scheduled Job Name** A, then select **Specified Job Schedule** from the **Calendar** drop-down.
3. Designate the **Date**, then click **SAVE**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-06-20_15h04_10.png)
4. Repeat the NEW AD SYNC JOB process four more times, providing the names B, C, D, and E.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-06-20_15h06_20.png)
5. Right-click **Job C** and select **Edit Scheduled Job**.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2024-06-20_15h06_48.png)
6. Scroll down to **ADVANCED > Values** and enter **My Queue Y** into **Override Job Queue Name**, then click **OK** to save. ![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-12-31_11h01_22.png)
7. Repeat this process for **Job D**, being sure to specify Override Job Queue Name as My Queue Y; click OK to save.![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-12-31_11h07_14(2).png)
8. Edit Job E, specifying the Override Job Queue Name value as **My Queue Z**, then click OK to save. If all these jobs are scheduled to start at 5 PM, three of the five jobs (**Job A**, **Job C,** and **Job E** ) will start at that time because the jobs are in three separate queues (Default pool, My Queue Y, and My Queue Z).  
  
Because **Job A** is in the same pool as **Job B**, **Job B** will not begin until **Job A** has been completed. Because **Job C** is in the same pool as **Job D**, **Job D** will not begin until **Job C** has been completed.  
  
However, **Job C** will begin at the scheduled time because it is in a different pool than **Job A** and **Job B**. Because **Job E** is in its own pool, it will start at the scheduled time regardless of which other jobs have also started at that time.

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/2020-12-31_11h11_47.png)