> For the complete documentation index, see [llms.txt](https://docs.owkin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.owkin.com/help-center/running-analyses-and-working-with-results/missing-values-in-plots-tables-and-counts.md).

# Why does my plot, table or count show missing values?

{% hint style="info" %}
**What this article covers** This article explains the most common reasons why K-Pro shows empty values, or says that some information is not available, and what to do.
{% endhint %}

### A variable is not in your dataset version

K-Pro can only use variables that are loaded in the data version of your instance. If a variable is missing, K-Pro may use a different column or tell you that the information is not available.

* Check the Dataset Catalog to see which variables exist.
* If a variable you need is missing, tell us its exact name. A new data release may add it.

### Tumour-subclone values need matching single-cell data

Some spatial cell-type values are computed for each sample, and only when the same tissue block also has single-cell data. Where there is no match, the values are empty. This is a data gap, not a software error.

### Some values are only computed inside the tumour core

Some histology features, such as cell densities inside the tumour, are computed only when a tumour core is detected on the slide. When none is detected, these features are not computed and appear as missing.

### What to do

1. Open the Dataset Catalog and check that the dataset and variable are included in your instance.
2. Rephrase your question to name the variable you expect.
3. If the value is still missing, contact support with the link to the conversation and what you expected to see. We tell you whether the data is missing or whether something needs fixing.

***

**✉️ Need more help?**\
If this article did not answer your questions, please [contact our support team](https://k-pro.zendesk.com/hc/en-us/requests/new?ticket_form_id=33609591380241) and we will be happy to help.


---

# 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.owkin.com/help-center/running-analyses-and-working-with-results/missing-values-in-plots-tables-and-counts.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.
