> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/powershell-universal/powershell-commands/get-psuschedule.md).

# Get-PSUSchedule

Get-PSUSchedule retrieves job schedules defined in PowerShell Universal, filterable by ID, name, identity, or script.

## SYNOPSIS

Retrieves schedules defined in PowerShell Universal.

## SYNTAX

```powershell
Get-PSUSchedule [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Get-PSUSchedule -Id <Int64> [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Get-PSUSchedule -Name <String> [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Get-PSUSchedule -Identity <Identity> [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
Get-PSUSchedule -Script <Script> [-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]
```

## DESCRIPTION

Returns reusable, cron, continuous, and one-time schedules. Schedules may target scripts or workflows; use the returned schedule object with `Set-PSUSchedule` to update its target, parameters, or timing. `-Identity` and `-Script` accept pipeline input by value.

## EXAMPLES

```powershell
Get-PSUSchedule -Name 'Nightly Cleanup'
$script = Get-PSUScript -Name 'Cleanup.ps1'
Get-PSUSchedule -Script $script
```

## PARAMETERS

| Parameter                | Description                                                               |
| ------------------------ | ------------------------------------------------------------------------- |
| `-Id`                    | Numeric schedule ID.                                                      |
| `-Name`                  | Schedule name.                                                            |
| `-Identity`              | Return schedules created by this identity; accepts pipeline input.        |
| `-Script`                | Return schedules for this script; accepts pipeline input.                 |
| `-ComputerName`          | PSU server URL for a remote management connection; alias: `-Uri`.         |
| `-AppToken`              | App token for a remote management connection.                             |
| `-Credential`            | Credentials for the management API.                                       |
| `-UseDefaultCredentials` | Use the current Windows credentials for the management connection.        |
| `-Integrated`            | Use the in-process PSU management client when the cmdlet runs inside PSU. |
| `-TrustCertificate`      | Allow a remote connection with an untrusted TLS certificate.              |
| `-Cookies`               | Reuse and persist authentication cookies in this PowerShell session.      |

## PERMISSIONS

The access token requires `automation.schedules/read` to run this cmdlet remotely.


---

# 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.devolutions.net/powershell-universal/powershell-commands/get-psuschedule.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.