> For the complete documentation index, see [llms.txt](https://platform9.com/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://platform9.com/kb/pmo/how-to/incorrect-total-count-of-instances-displayed-in-ui.md).

# Incorrect Total Count of Instances Displayed in UI

## Problem

The total count of Instances displayed in UI is Incorrect.

## Environment

* Platform9 Managed OpenStack - v3.11.0 and Higher

## Cause

The server responds with ‘server\_links’ if there are more instances to list. In this case, the link was not correctly built.

## Answer

* The patch is configured to attempt a new call setting marker as the last instance ID until the API returns an empty list for instances.
* The patch is under testing and this article will be updated once the patch is included in an upcoming release.


---

# 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://platform9.com/kb/pmo/how-to/incorrect-total-count-of-instances-displayed-in-ui.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.