---
sourceDocument: Australia Sales and Order Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/order-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Sales and Order Management

ft:clusterId :

    - omgmt

bundleId :

    - omgmt

workflow :

    - Customer and Industry


---

# Circular references in rules and fields

# Circular references in rules and fields {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Circular references in a blueprint may result in an error.

CPQ Admin allows administrators to define a blueprint whose rules and fields result in a circular reference. If the end user enters configuration inputs that initiate an endless loop, an error state occurs.

For example, suppose rule 1 consists of a condition on field A and a determination action that sets field B, while rule 2 has a condition on field B and a determination action that sets field B. These interacting rules would create
an endless loop.

Loops may also be composed of many fields and rules. In more complex use cases, it is common for testers and end users to successfully operate the configuration blueprint without encountering the error state. The CPQ Rule Cycle Report identifies potential loops so that the administrator can understand their risk and correct them.

To identify endless loops in a blueprint, use the Rule Cycle Report. See [Identify endless loops in blueprint rules](https://servicenow-prod.fluidtopics.net/K~TBTrHN1h~b4FdL2aSR_g "Use the Rule Cycle Report to identify endless loops that may be hard to find during ordinary operation.").
**Zugehörige Tasks**   

* [Identify endless loops in blueprint rules](https://servicenow-prod.fluidtopics.net/K~TBTrHN1h~b4FdL2aSR_g "Use the Rule Cycle Report to identify endless loops that may be hard to find during ordinary operation.")