> For the complete documentation index, see [llms.txt](https://docs.nexthink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nexthink.com/references/references-classic/search-and-information-display-classic/top-results-of-cross-engine-investigations-with-finder-classic.md).
# Top results of cross-Engine investigations with Finder (classic)
### Overview
Investigations that return a specified number of [top objects](/user-guide/investigations/creating-an-investigation-with-finder-classic/editing-the-options-of-an-investigation-with-finder-classic.md), which are ordered according to a particular criterion, may yield surprising results when targeting multiple Engines simultaneously.
Learn how these top investigations are executed in Cross-Engine contexts to avoid misunderstandings.
### Individual execution of top investigations
When targeting multiple Engines, a top investigation first executes on each Engine individually and then aggregates the results. For instance, suppose that you are looking for the top 4 domains ordered by the highest number of visiting devices across two Engines.
| Engine 1 | Engine 1 | Engine 2 | Engine 2 |
| ------------------------ | --------------------------- | ------------------------ | --------------------------- |
| Domain | Number of
Devices
| Domain | Number of
Devices
|
| `community.nexthink.com` | 300 | `community.nexthink.com` | 350 |
| `docs.nexthink.com` | 200 | `www.nexthink.com` | 150 |
| `www.nexthink.com` | 150 | `docs.nexthink.com` | 50 |
| `design.nexthink.com` | 50 | `design.nexthink.com` | 40 |
The Cross-Engine investigation returns the total number of devices by adding the results in both Engines.
| Domain | Number of Devices |
| ------------------------ | ----------------- |
| `community.nexthink.com` | 650 |
| `www.nexthink.com` | 300 |
| `docs.nexthink.com` | 250 |
| `design.nexthink.com` | 90 |
### Aggregation of different top results
However, imagine that you repeat the same investigation, but you only ask for the top two domains with the highest number of visiting devices. In this case, the individual execution on each Engine returns a different list of domains:
| Engine 1 | Engine 1 | Engine 2 | Engine 2 |
| ------------------------ | --------------------------- | ------------------------ | --------------------------- |
| Domain | Number of
Devices
| Domain | Number of
Devices
|
| `community.nexthink.com` | 300 | `community.nexthink.com` | 350 |
| `docs.nexthink.com` | 200 | `www.nexthink.com` | 150 |
Results beyond the second domain are lost. Thus, the aggregation of results ignores anything after the second position and the Cross-Engine investigation returns the following:
| Domain | Number of Devices |
| ------------------------ | ----------------- |
| `community.nexthink.com` | 650 |
| `docs.nexthink.com` | 200 |
While we might expect to find the domain `www.nexthink.com` in second place with 300 devices, as in the previous top four investigations, we instead see that `docs.nexthink.com` comes in second place with 200 devices because the aggregation is ignoring the values beyond the second place in both Engines. Keep this behavior in mind when writing Cross-Engine top investigations with aggregates that are added up.
---
# 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.nexthink.com/references/references-classic/search-and-information-display-classic/top-results-of-cross-engine-investigations-with-finder-classic.md?ask=&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.