---
title: "Circular dependency detected (prevented)."
canonical: "https://support.appfire.com/space/DLP/297045895/Circular%20dependency%20detected%20(prevented)."
format: markdown
---
<span style="color: #172b4d">If you can see this message, there would be a circular dependency if the shift action defined by structure builders was performed. </span>

![image](media://e686dfc5-bfd9-475e-ba03-9f0a5feabef6)

## Why do I see this message? 

[Task structure](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297573588) rules conflict.

Rules with an opposite effect have been created (in two different Boxes that share at least part of their scope). Those rules are trying to produce contradictory results:

![image](media://21bf5bba-e85c-4bbc-a9d6-be090ad82d2b)

## How to fix the issue?

> ℹ️ Changes to the WBS structure haven't been applied because of the conflict. To fix the issue:
> ℹ️ 
> ℹ️ - Correct the task structure rules in one of the affected Boxes
> ℹ️ - or change the task details to ensure all Box rules can be applied at the same time
> ℹ️ 
> ℹ️ **Once the issue has been addressed, clear the warning log and trigger a data re-sync.**

## Case 1 - Inverse vs. normal use of link-based structure builders

> ℹ️ Any "link-based" structure builders can lead to this situation because they have the "inverse" option.

![image2022-3-11_8-19-55.png](media://eed01ec3-16f3-4eec-bf2c-4b528f1d0e0e)

The app can't fulfill the setup when:

- Tasks are in two separate Boxes (Boxes share at least part of their scope)
- "link-based" structure builders have been used to create a WBS structure (in one Box, the "inverse" checkbox has been selected; in the other one, it's empty).

Those rules have the opposite effect. They would produce contradictory results:  


![image2022-3-11_8-15-33.png](media://21bf5bba-e85c-4bbc-a9d6-be090ad82d2b)

In the example, the "Relates" link type has been used:

- Normal links:
- Inverted links:

  


## Case 2 - structure builders in the opposite order

Different order of structure builders in two Boxes (with the same scope).

![image](media://12f9cddf-860e-45ea-bfc1-8247deea0dd9)

The two Boxes share at least part of their scope:

![image2022-3-11_7-39-54.png](media://224ac248-5d12-4a97-9906-a8e655133ed0)

Those rules would try to create an opposite parent-child relationship in those Boxes (both can't be true simultaneously).