> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/qna/using-navixy/event-count-inconsistency-when-selecting-multiple-devices.md).

# Event count inconsistency when selecting multiple devices

## Question

Why are all events displayed correctly when a single device is selected, but they change when multiple devices are selected?

<figure><img src="/files/z1i5Yg5U9ZMyWTPNomCA" alt=""><figcaption></figcaption></figure>

## Answer

This behavior is expected and is related to the way the History Tracker API applies its event limit.

According to the public documentation:

> <mark style="color:$info;">limit – Default and maximum value is 1000 (for StandAlone this is configurable through</mark> <mark style="color:$info;">`maxHistoryLimit`</mark><mark style="color:$info;">).</mark>

The important detail is that the limit is applied to the entire request, not individually to each selected tracker. In other words, the server returns up to 1000 of the most recent events across all selected devices, rather than up to 1000 events per device.

#### Example

* **1 device selected**
  * The device has 59 events.
  * Since the total is well below the limit, all 59 events are returned.
* **22 devices selected**
  * The combined number of events is still below the limit.
  * The device continues showing 59 events.
* **All devices selected**
  * Some devices generate events much more frequently than others.
  * The server returns only the 1000 most recent events across the entire selection.
  * As a result, older events from less active devices may be excluded from the response.
  * In this scenario, the selected device displays only 32 events, even though it originally had 59.

The event pool is shared among all selected devices. The more devices included in the request—especially those generating a high volume of events—the greater the chance that older events from other devices will fall outside the 1000-event limit.

Currently, the frontend does not indicate when the returned event list has been truncated due to the global limit, which may lead users to believe that events are missing when they have simply been excluded by the API limit.

## Links

[API- Tracker events](https://navixy.com/docs/navixy-api/user-api/backend-api/resources/commons/history/history_tracker)

[Event History](https://navixy.com/docs/user/guide/tracking/history-view/event-history#event-details)


---

# 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://navixy.com/docs/qna/using-navixy/event-count-inconsistency-when-selecting-multiple-devices.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.