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

# Applications

Find the cause and the fix for common Applications problems.

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

<details>

<summary>Credit Decisioning shows "Waiting to be claimed"</summary>

**Why:** Nobody has claimed the application, so the decision actions aren't available.

**What to do:** Claim the application. See [Application Record](broken://pages/JFF4ngUInPlRk5SpVF7A).

</details>

<details>

<summary>The applicant sees a read-only "Reference preview" and can't submit</summary>

**Why:** The product has no application flow of its own, so its sections appear as a read-only preview.

**What to do:** Build the product's flow on **Application Flow** before you set the product to **Active**. See [Application Flow](broken://pages/jft1YA1uw5NGn0Y68mcX).

</details>

<details>

<summary>A product doesn't appear when an applicant starts</summary>

**Why:** The product is **Inactive** or **Suspended**, or its **Category** doesn't match the applicant.

**What to do:** Check the product's **Status** and **Category**. See [Starting an Application](broken://pages/802GfCWuEgm8kc5qwK7F).

</details>

<details>

<summary>A failed verification declined the applicant, and you wanted a person to look</summary>

**Why:** What happens after a failed verification is set in the product's **Workflow**.

**What to do:** Route the outcomes you want a person to look at to **Manual review** rather than to a decline. See [Starting an Application](broken://pages/802GfCWuEgm8kc5qwK7F).

</details>

<details>

<summary>The status is the same after you returned an application to intake</summary>

**Why:** Returning to intake changes the stage, but the status can stay the same, for example *Manual review*.

**What to do:** Check the status after you move the application between stages. See [Work an Application](broken://pages/lvXMbbnbRDUhZZqPPeJE).

</details>

<details>

<summary>The workflow timeline shows durations but no target comparison</summary>

**Why:** No step has a target time.

**What to do:** Add an SLA or timeout to a step in the product's workflow. See [Workflow Timeline](broken://pages/oH9buEhKL7c4OSqdWm2x).

</details>

<details>

<summary>A tab is missing on an application</summary>

**Why:** The tabs come from the product's **Tab Settings**, and a role sees a tab only if it has view permission for it.

**What to do:** Check the product's **Tab Settings**, then the role's permissions. See [Module Access](broken://pages/EebOasKPKQhWq9ggrFQL).

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