> For the complete documentation index, see [llms.txt](https://docs.alemba.com/asm-hermes/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/workflow-template-administration/managing-tasks-adding-tasks-to-the-dependency-diagram/task-types-in-the-task-palette/creating-a-closure-task.md).
# Creating a Closure Task
A request can have multiple Closure tasks depending on the workflow path. They can be automated or manually run by an analyst.
{% hint style="warning" %}
If the request does not have a closure task, the request manager must manually close the request.
{% endhint %}
You have the same options for closing the request within a closure task as you do when performing the completion within the request itself. Success and failure can still be specified, as can additional information about the nature of the success or failure and descriptive information. Email notifications can also be sent.
Example: This screen can be customised in Screen Designer in order to capture exactly the information needed.
{% hint style="info" %}
If a closure task becomes active and attempts to close a request while it is currently being actioned on by the request manager, the closure task will automatically complete once the request is free. A note will be added to the task history stating that the completion of the closure task has been delayed due to the request being locked.
{% endhint %}
### Creating a Closure Task
1. On the **dependency diagram**, double-click the icon to view the **Change Window Task Details** window.
2. Complete the common task fields on this task. ***See Also:*** [***Creating a Task***](https://docs.alemba.com/asm-hermes-10.6.8/setup-and-configure-asm/configuring-your-system/workflow-template-administration/steps-for-workflow-request-template-creation/managing-tasks-adding-tasks-to-the-dependency-diagram/task-types-in-the-task-palette/creating-a-task)
3. Expand the **Implementation Details** section to set the request closure parameters.
4. After you have completed the fields, save the task
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.alemba.com/asm-hermes/setup-and-configure-asm/configuring-your-system/workflow-template-administration/managing-tasks-adding-tasks-to-the-dependency-diagram/task-types-in-the-task-palette/creating-a-closure-task.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.