# Shutdown Sequence

Workers in an application's call-chain are shutdown from the bottom up, with the shutdown command of each Worker first cascading down the Worker call-chain hierarchy from the top.

When a Worker has been shutdown (exited), it notifies its Caller. This confirmation comes from the bottom up, in a **reverse** cascade back up the Worker call-chain hierarchy.

The following flowchart explains the shutdown sequence of a Workers application.

{% hint style="info" %}
While the diagram below shows the shutdown sequence for an application starting with the application's head Worker, the shutdown sequence can be started on any Worker by use of the Workers palette VI: *Worker Start Exiting.vi.* This will shutdown only the specified Worker and its subWorkers. Any Workers above this Worker (in the applications Worker call-chain hierarchy) will not be shutdown.
{% endhint %}

![Shutdown sequence of a Workers application (note: Manager means Caller in this diagram)](/files/TDNdDxHxcwDMdO5iVHDk)


---

# Agent Instructions: 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:

```
GET https://docs.workersforlabview.io/fundamental-concepts/shutdown-sequence.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.