> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/deployr/reference/step-definitions/suspend-task-sequence.md).

# Suspend task sequence

The **Suspend task sequence** step stops the task sequence temporarily so that a technician can do manual work on the device, then resume the task sequence where it left off. This step has no options.

When the step runs, the task sequence exits and leaves the automatically signed-in session at the desktop. The step creates a **Continue DeployR** shortcut on the public desktop. Double-click the shortcut to resume the task sequence with the step after **Suspend task sequence**. The shortcut is removed when the task sequence resumes.

### Requirements

* Run this step in the full OS. It fails in Windows PE.
* The OS must have been deployed with the **Use AutoAdminLogon and RunOnce** continuation method. With any other continuation method, the step fails.

Unlike the [Pause](/deployr/reference/step-definitions/pause.md) step, which keeps the task sequence and progress UI running until someone clicks **Continue**, this step ends the task sequence process, so the device can be used normally while it is suspended.


---

# 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://documentation.2pintsoftware.com/deployr/reference/step-definitions/suspend-task-sequence.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.