> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2021.1-changes-overview/work-manager/wait-for-sub-cases-to-complete-actions-improvements.md).

# 'Wait for Sub-Cases to Complete' Action Improvements

v2021.1

Once a Sub-Case has been launched (either manually or through a 'Start Case' Action), a ‘Wait for Sub-Cases to Complete’ Action will move into a state of 'Waiting' for all currently running Sub-Cases within a Case to reach completion before allowing the Case to complete.

![](https://gblobscdn.gitbook.com/assets%2F-MR4uErt41EMkGUOTvyd%2F-Mahf7s_DMYD56EJBY03%2F-MahjL3C13RNC2jFgHiy%2Fimage.png?alt=media\&token=7d6c2eb3-78c8-4b0a-a6c5-6c79a272dbba)

Once the Sub-Case is completed, the 'Wait for Sub-Cases to Complete' Action will close automatically.

![](https://gblobscdn.gitbook.com/assets%2F-MR4uErt41EMkGUOTvyd%2F-MahUFjily7RQQJpY-ey%2F-MaheDU9F_gMsejOp3Id%2Fimage.png?alt=media\&token=37e002c4-5517-4301-b605-f568d39c1db5)

If a Sub-Case has not been launched but a ‘Wait for Sub-Cases to Complete’ Action HAS been launched, the ‘Wait for Sub-Cases to Complete’ Action will enter a 'To Do' state and be assigned to a Queue.

![](https://gblobscdn.gitbook.com/assets%2F-MR4uErt41EMkGUOTvyd%2F-M_tt8kvvrs8MMHHKag6%2F-M_ttFIUdXov1PCb7v2Z%2Fimage.png?alt=media\&token=abd4dab3-54ef-4172-930a-09775d9106cd)

If the Action is not in 'Wait for Sub-Cases to Complete' state and the Sub-Case for which it is waiting has been completed, a message will appear as 'Sub-Case is completed in the Info Card.

![](https://gblobscdn.gitbook.com/assets%2F-MR4uErt41EMkGUOTvyd%2F-Mahf7s_DMYD56EJBY03%2F-MahjJ5dRBh27P7pDi6T%2Fimage.png?alt=media\&token=cf9a40b1-9f4e-4195-ae20-6b17596a4c90)

If the Sub-Case is not yet launched and if you try to set the Action to 'Waiting for Sub-Case to Complete', the Action will close as there is no Sub-Case launched.

If you try to manually Resolve a ‘Wait for Sub-Case to Complete’ Action, the system will inform you that the main Case will no longer wait for Sub-Case completion before it completes itself.

![](https://gblobscdn.gitbook.com/assets%2F-MR4uErt41EMkGUOTvyd%2F-MahUFjily7RQQJpY-ey%2F-MahXkdw7JGQmuPjwTlW%2Fimage.png?alt=media\&token=17fbf5e7-0de3-4dff-bcc1-cb1d6c1e2ebe)


---

# 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.enate.net/whats-new/older-versions/changes-overview-older-versions/2021.1-changes-overview/work-manager/wait-for-sub-cases-to-complete-actions-improvements.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.