> 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/invoke-psuschedule.md).

# Invoke-PSUSchedule

Déclencher immédiatement une planification PowerShell Universal par ID, nom ou objet de planification.

## SYNOPSIS

Déclenche l'exécution immédiate d'une planification PowerShell Universal.

## SYNTAXE

```powershell
Invoke-PSUSchedule -Id <Int64> [<ConnectionOptions>] [<CommonParameters>]
Invoke-PSUSchedule -Name <String> [<ConnectionOptions>] [<CommonParameters>]
Invoke-PSUSchedule -Schedule <Schedule> [<ConnectionOptions>] [<CommonParameters>]
```

`<ConnectionOptions>`: `[-ComputerName <String>] [-AppToken <String>] [-Credential <PSCredential>] [-UseDefaultCredentials] [-Integrated] [-TrustCertificate] [-Cookies]`.

## DESCRIPTION

Déclenche une planification existante par le même chemin d'exécution que la console d'administration. Sélectionnez-la par ID numérique, par nom sans égard à la casse ou par un objet `Schedule` de `Get-PSUSchedule` transmis par le pipeline. Un objet de planification doit avoir un ID ou un nom valide ; une planification inconnue produit une erreur.

## EXEMPLES

```powershell
Invoke-PSUSchedule -Id 10
Invoke-PSUSchedule -Name 'Nightly maintenance'
Get-PSUSchedule -Name 'Nightly maintenance' | Invoke-PSUSchedule
```

## PARAMÈTRES

| Paramètre                | Description                                                  |
| ------------------------ | ------------------------------------------------------------ |
| `-Id`                    | ID numérique de la planification à déclencher.               |
| `-Name`                  | Nom de la planification à déclencher, sans égard à la casse. |
| `-Schedule`              | Objet de planification ; accepte l'entrée du pipeline.       |
| `-ComputerName`          | URL ou nom d'hôte de l'API de gestion PSU (alias `-Uri`).    |
| `-AppToken`              | Jeton d'application de l'API de gestion.                     |
| `-Credential`            | Identifiants de l'API de gestion.                            |
| `-UseDefaultCredentials` | Utilise les identifiants Windows actuels.                    |
| `-Integrated`            | Utilise le client de gestion dans le processus.              |
| `-TrustCertificate`      | Ignore les erreurs de validation du certificat.              |
| `-Cookies`               | Réutilise les témoins d'authentification de la session.      |

## SORTIES

Aucune.

## LIENS CONNEXES

[Get-PSUSchedule](/powershell-universal/fr/commandes-powershell/get-psuschedule.md) · [New-PSUSchedule](/powershell-universal/fr/commandes-powershell/new-psuschedule.md)

## PERMISSIONS

Le jeton d'accès requiert `automation.schedules/execute` 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/invoke-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.