> For the complete documentation index, see [llms.txt](https://docs.workersforlabview.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.workersforlabview.io/workers-tools/quickdrop-shortcuts/go-to-mhl-case-ctrl+8.md).

# Go To MHL Case (Ctrl+8)

This Quickdrop shortcut allows you to follow the flow of messages around a Workers application while you are developing in LabVIEW. Activating this Quickdrop shortcut on one of the following VIs will jump directly to the corresponding MHL case of the VI. This Quickdrop shortcut works with the following VIs:

* Case Labels
* Local API Request VI
* Public API Request VI
* Public API Request with Reply VI
* Public API Response VI (this will jump to the location of the corresponding Response VTD VI)

### Step 1: Select a Case Label  or Worker API VI on a block diagram

Select a Case Label or Worker API VI on the block diagram of a VI.

![rqp\_Start.vi (Public Request VI) selected](/files/5s3WVlMAW2FVmd0uqhAe)

### Step 2: Activate Quickdrop shortcut Ctrl+8

With the VI selected, activate Quickdrop shortcut Ctrl+8. The corresponding MHL case of the Worker API VI or Case Label should now appear.

![The Public API MHL case of rqp\_Start.vi will appear](/files/CmCq5NmT0VZxgyrbqiVV)


---

# 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.workersforlabview.io/workers-tools/quickdrop-shortcuts/go-to-mhl-case-ctrl+8.md?ask=<question>&goal=<endgoal>
```

`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.