> 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/configurations.md).

# Configurations

Find the cause and the fix for common Configurations problems.

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

<details>

<summary>Loan officers can't record a kind of collateral</summary>

**Why:** Collateral is always recorded against an asset type, and the type needs to be active.

**What to do:** Add or activate the asset type. **Add Asset Type** is in the action rail, not the page header. See [Manage Asset Types](broken://pages/2gjInEZ1ijLhb1Sw84kM).

</details>

<details>

<summary>A document type is gone</summary>

**Why:** Deleting a document type is permanent, and you can delete **System** types as well as **Custom** ones.

**What to do:** Add the type again in the **Doc Registry**. Before you delete a type, check that no product checklist or open application still requests it. See [Manage Document Types](broken://pages/9xdgJ0sOqwkTqnz9z3DB).

</details>

<details>

<summary>A system email stopped going out</summary>

**Why:** Retail LOS sends system emails by internal key, so deleting a standard template can stop that email.

**What to do:** Check that none of the 18 standard templates was deleted. See [Manage Email Templates](broken://pages/e1YTIN4iJ9k9dztOwpOD).

</details>

<details>

<summary>Document merge order changes don't take effect</summary>

**Why:** The **JSON Editor** ignores invalid JSON without a warning.

**What to do:** Check the JSON before you save. Remove empty rows too, since **Save Configuration** is available even when rows are empty. See [Set the Document Merge Order](broken://pages/8unIrYqBKBVhKzkuPc3I).

</details>

<details>

<summary>Applications are sitting unworked</summary>

**Why:** A status your teams work isn't covered by a queue, or a queue placed too high is taking applications meant for another team.

**What to do:** Check that every status is covered, then check the queue order. See [Manage Queues](broken://pages/Z5lL0LhJf641nu5qRvHP).

</details>

<details>

<summary>Applications moved to another queue after you removed one</summary>

**Why:** Removing a queue moves its waiting applications into whichever queue they match next.

**What to do:** Check the queue order before you remove a queue. The confirmation is a plain browser dialog, so it's easy to select through. See [Manage Work Queues](broken://pages/AcHGnKC5TVYfuZEeVRA0).

</details>

<details>

<summary>A quick action disappeared for everyone</summary>

**Why:** Changes apply to everyone who uses the page. Removing an action hides that shortcut from every user, not just from you.

**What to do:** Agree changes with the teams that use the page. **Discard** reverts immediately, without asking. See [Change Quick Actions](broken://pages/dy6Bmqa3r6wkTR5x1UD8).

</details>

<details>

<summary>The Bank Statement Analysis agent doesn't run</summary>

**Why:** The agent can't run until a default agent user is set.

**What to do:** Set one under **Settings** > **Integrations**. See [Bank Statement Analysis](broken://pages/k70w0BYbx0jCXxOOS2VI).

</details>

<details>

<summary>Notice deadlines saved with odd values such as 0</summary>

**Why:** The day and count fields don't warn you about unusual values such as 0 or a blank field.

**What to do:** Check every value before you select **Save Notice Settings**, and have compliance review the change. See [Set Up Notices](broken://pages/AoblDphRt9urqP1UaMc8).

</details>

<details>

<summary>A Record tab no longer shows on client pages</summary>

**Why:** The layout applies to every client page of that type, for all products. Deleting a tab definition removes it permanently.

**What to do:** To hide a tab without losing it, clear it instead of deleting it. See [Manage Record Tabs](broken://pages/JuKpxiz49Dp9K7vPMHa7).

</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/configurations.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.
