# Circular Dependency message

If you encounter a circular dependency error as shown in the image:

<figure><img src="/files/rGCKSX9fOQkb8SViMjCB" alt=""><figcaption><p>Image 1: Circular Dependency Error</p></figcaption></figure>

{% hint style="info" %}
The visual requires a clear and organized **Id** and **PId** data structure to create a hierarchical view. Although the visual logic is designed to handle a range of scenarios, some data structures may still not support hierarchy determination. In these cases, warning messages may appear to indicate the issue.

It is advised to clean or filter out such data to plot the hierarchy. If you are looking for connections between the nodes, then instead use [Links](/performance-management/links.md).&#x20;
{% endhint %}

Then these scenarios could be the possible reasons:

1. ID = Parent ID:

You encounter a circular dependency error when your ID is equal to PID in dataset, as shown in the image below:

<figure><img src="/files/xe3k9Cy1fJpRw4sEkDl6" alt="" width="214"><figcaption><p>Image 2: ID = Parent ID</p></figcaption></figure>

2. Two or more nodes are parents to each other:

You encounter a circular dependency error when two or more nodes are parents to each other in dataset, as shown in the image below:

<figure><img src="/files/mDdAI1vKyj2jVjkeTFNR" alt="" width="212"><figcaption><p>Image 3: Two nodes are parent to each other</p></figcaption></figure>

{% hint style="success" %}
These scenarios do not align with the expected structure for a hierarchy view in the visual and make it difficult to create the correct hierarchy structure based on the dataset.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.xviz.com/performance-management/faqs/circular-dependency-message.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
