> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/ams/v2.0/help-and-support/powershellmodule/get-amsjitschedulerjob.md).

# Get-AmsJitSchedulerJob

## SYNOPSIS

Gets the list of active just-in-time access jobs in the AMS scheduler

## SYNTAX

### GetByType (Default)

```
Get-AmsJitSchedulerJob [-Type <ScheduledTaskType>] [-FailedOnly] [<CommonParameters>]
```

### GetById

```
Get-AmsJitSchedulerJob [-Id] <String> [<CommonParameters>]
```

## DESCRIPTION

This cmdlet can be used to see the pending JIT removal tasks that are waiting in the scheduler.

## EXAMPLES

### Example 1

```powershell
PS C:\> Get-AmsJitSchedulerJob
```

Gets a list of all jobs pending in AMS scheduler

### Example 2

```powershell
PS C:\> Get-AmsJitSchedulerJob -FailedOnly
```

Gets a list of all jobs in the AMS scheduler that have failed to successfully execute the JIT removal operation

### Example 3

```powershell
PS C:\> Get-AmsJitSchedulerJob -Id 'XXXXXX'
```

Gets a specific JIT scheduler job by its ID

## PARAMETERS

### -FailedOnly

Instructs the cmdlet to only return jobs that have failed to execute the JIT removal operation

```yaml
Type: SwitchParameter
Parameter Sets: GetByType
Aliases:

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### -Id

The ID of the job

```yaml
Type: String
Parameter Sets: GetById
Aliases:

Required: True
Position: 1
Default value: None
Accept pipeline input: True (ByPropertyName)
Accept wildcard characters: False
```

### -Type

The type of JIT scheduler job to return

```yaml
Type: ScheduledTaskType
Parameter Sets: GetByType
Aliases:
Accepted values: ActiveDirectoryGroupRemoval

Required: False
Position: Named
Default value: None
Accept pipeline input: False
Accept wildcard characters: False
```

### CommonParameters

This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about\_CommonParameters](http://go.microsoft.com/fwlink/?LinkID=113216).

## INPUTS

### System.String

## OUTPUTS

### Lithnet.AccessManager.PowerShell.ActiveDirectoryGroupMemberRemovalJobDetailsPSObject

## NOTES

In an Active Directory forest, with the `Privilege Access Management` feature enabled, AMS will use TTL-based group membership for Active Directory JIT tasks. The AMS JIT scheduler will not be used, and no jobs will appear in the scheduler queue

## RELATED LINKS


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lithnet.io/ams/v2.0/help-and-support/powershellmodule/get-amsjitschedulerjob.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
