> 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/fr/commandes-powershell/get-psuschedule.md).

# Get-PSUSchedule

Get-PSUSchedule récupère les planifications de tâches définies dans PowerShell Universal, filtrables par ID, nom, identité ou script.

## SYNOPSIS

Récupère les planifications définies dans PowerShell Universal.

## SYNTAXE

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

Retourne les planifications réutilisables, cron, continues et uniques. Les planifications peuvent cibler des scripts ou des flux de travail ; utilisez l'objet de planification retourné avec `Set-PSUSchedule` pour mettre à jour sa cible, ses paramètres ou son horaire. `-Identity` et `-Script` acceptent l'entrée du pipeline par valeur.

## EXEMPLES

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

## PARAMÈTRES

| Paramètre                | Description                                                                                                      |
| ------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| `-Id`                    | ID numérique de la planification.                                                                                |
| `-Name`                  | Nom de la planification.                                                                                         |
| `-Identity`              | Retourne les planifications créées par cette identité ; accepte l'entrée du pipeline.                            |
| `-Script`                | Retourne les planifications de ce script ; accepte l'entrée du pipeline.                                         |
| `-ComputerName`          | URL du serveur PSU pour une connexion de gestion distante ; alias : `-Uri`.                                      |
| `-AppToken`              | Jeton d'application pour une connexion de gestion distante.                                                      |
| `-Credential`            | Identifiants pour l'API de gestion.                                                                              |
| `-UseDefaultCredentials` | Utilisez les identifiants Windows actuels pour la connexion de gestion.                                          |
| `-Integrated`            | Utilisez le client de gestion PSU dans le processus lorsque l'applet de commande s'exécute à l'intérieur de PSU. |
| `-TrustCertificate`      | Autorise une connexion distante avec un certificat TLS non approuvé.                                             |
| `-Cookies`               | Réutilisez et conservez les témoins d'authentification dans cette session PowerShell.                            |

## PERMISSIONS

Le jeton d'accès requiert `automation.schedules/read` pour exécuter cette applet de commande à distance.


---

# 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/fr/commandes-powershell/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.