> 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/automation/schedules/run-schedules-with-powershell.md).

# Run schedules with PowerShell

Use Invoke-PSUSchedule to trigger an existing PowerShell Universal schedule immediately, using the same execution path as the admin console.

Use `Invoke-PSUSchedule` to trigger an existing schedule immediately. It uses the same execution path as the admin console, so the schedule keeps its configured script, environment, credential, computer target, and other run options.

The caller requires **Automation Schedules** execute permission.

## Select a schedule

Trigger a schedule by ID:

```powershell
Invoke-PSUSchedule -Id 10
```

Trigger a schedule by name:

```powershell
Invoke-PSUSchedule -Name 'Nightly maintenance'
```

You can also pipe a schedule object:

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

`Invoke-PSUSchedule` starts a new run; it does not change the schedule definition or its next scheduled execution.


---

# 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/automation/schedules/run-schedules-with-powershell.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.