> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/retail-lending/help-center/troubleshooting/product-configuration.md).

# Product Configuration

Find the cause and the fix for common Product Configuration problems.

Each item gives what you see, why it happens, and what to do.

<details>

<summary>Every application goes to Manual review</summary>

**Why:** The decision matrix may be saved but not published, so a draft is never used. A too-strict auto-approval rule has the same effect: anyone not meeting it goes to manual review.

**What to do:** Publish after testing in the Simulator, and review the auto-approval rules together with the tiers. See [Common Mistakes](broken://pages/cFDwjWwjywK0MbNttGp4).

</details>

<details>

<summary>The Run scorecard step returns NOT_CONFIGURED</summary>

**Why:** The product has no scorecard version.

**What to do:** Create and activate a scorecard on **Scorecard Settings**. See [Scorecard Settings](broken://pages/GtXXWkUUkY8RY2brDBmz).

</details>

<details>

<summary>Applications with a scorecard go to manual underwriting review</summary>

**Why:** An application that matches no tier rule goes to manual underwriting review.

**What to do:** Make sure the last tier rule catches every score you're willing to decide automatically. See [Scorecard Settings](broken://pages/GtXXWkUUkY8RY2brDBmz).

</details>

<details>

<summary>Every application passes the scorecard</summary>

**Why:** The passing score is below the lowest achievable score, so the pass or fail check has no effect.

**What to do:** Set the passing score above the lowest achievable score. See [Scorecard Settings](broken://pages/GtXXWkUUkY8RY2brDBmz).

</details>

<details>

<summary>A rule can't use the data field you want</summary>

**Why:** Rules can use only the criteria defined in **Policy Criteria**.

**What to do:** Add the criterion in **Policy Criteria** first. See [Credit Decision Matrix](broken://pages/bSCpQ83uxYlKtmidq2n9).

</details>

<details>

<summary>You can't publish the decision matrix</summary>

**Why:** A version can't be published if any tier falls outside the product's limits. The **Limits Compliant** chip lists the violations.

**What to do:** Bring the tiers inside the product's limits, then publish. See [Decisions, Pricing, Offers](broken://pages/jo3OJEsRNxMSgOW8D09V).

</details>

<details>

<summary>A tab doesn't show for a role</summary>

**Why:** A tab appears for a role only if that role has view permission for the tab and its data.

**What to do:** Grant the role view permission after you add the tab. See [Choose a Product's Tabs](broken://pages/qq4RZQIjHeWeHpC4UhOv).

</details>

<details>

<summary>A document shows "Not linked to registry"</summary>

**Why:** The document was added before the registry had the type.

**What to do:** Add the document type to the Doc Registry first. See [Common Mistakes](broken://pages/cFDwjWwjywK0MbNttGp4).

</details>

<details>

<summary>Applicants don't see the eligibility questions</summary>

**Why:** Applicants see the gates only if the intake flow has an **Eligibility** step, placed before the steps that collect personal details.

**What to do:** Add an **Eligibility** step in the right place. See [Documents, Disclosures, and Eligibility](broken://pages/IZyXaFaXK4lODJk6aTLS).

</details>

<details>

<summary>A per-borrower step can show only one sub-step</summary>

**Why:** A step with **Party Scope (Multi-Borrower)** turned on can show only one sub-step per party.

**What to do:** Move the sections onto one sub-step and delete the others. See [Application Flow](broken://pages/jft1YA1uw5NGn0Y68mcX).

</details>

<details>

<summary>A step lost its content when you changed its type</summary>

**Why:** Changing a step from **Standard** to another type removes its sub-steps and their content.

**What to do:** Check before you change a step type. See [Flow Designer](broken://pages/ppvXFPRK3dMvYLASFBML).

</details>

<details>

<summary>A workflow change took effect straight away</summary>

**Why:** **Publish** takes effect immediately, without asking you to confirm.

**What to do:** Check that the check result is **Valid** before you publish, and build and test changes on an inactive copy of the product. See [Workflow](broken://pages/HtrMw5Rb28SNfizcpoDI).

</details>

<details>

<summary>A rule compares DTI 0.36 instead of 36%</summary>

**Why:** DTI was typed as 0.36, so the rule compares 0.36%.

**What to do:** Type percentages as 36. See [Common Mistakes](broken://pages/cFDwjWwjywK0MbNttGp4).

</details>

***

{% columns %}
{% column width="83.33333333333334%" %}

<p align="right"><em>Maintained by</em> <mark style="color:green;">Abhishek Paul</mark><br><code>AI-assisted, human-approved</code></p>
{% endcolumn %}

{% column width="16.666666666666664%" %}

<div align="left"><img src="https://2966508920-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ff06WQMAu97E0STor0yyS%2Fuploads%2Fgit-blob-d034645b4f8f8ee661985f5306b60ded3289653c%2Fmaintainer-abhishek-paul.png?alt=media" alt="" width="60"></div>
{% endcolumn %}
{% endcolumns %}


---

# 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.uptiq.ai/retail-lending/help-center/troubleshooting/product-configuration.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.
