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

# Logs

Find the cause and the fix for common Logs problems.

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

<details>

<summary>A notice shows Failed or Needs posting</summary>

**Why:** These notices need action from your team.

**What to do:** Act before the **Deadline**. See [Notice Logs](broken://pages/JFW2ZfWBGd22BUMHJOXX).

</details>

<details>

<summary>An operation has no user and shows HTTP 401</summary>

**Why:** It's a request that arrived without a valid sign-in.

**What to do:** Check whether you expected a signed-in user for that request. See [Operation Logs](broken://pages/hJqFBHgMmKwytSqlXuJE).

</details>

<details>

<summary>An error message says [attempt 1/3] and Retrying in 2s</summary>

**Why:** Retail LOS retried the integration call.

**What to do:** Check later steps in the same trace to see whether a retry succeeded. See [Request Traces](broken://pages/OlPHusyd9SSUndchum7V).

</details>

<details>

<summary>You can't tell where a change made in the staff portal came from</summary>

**Why:** Many changes made in the staff portal have no channel and show "-".

**What to do:** Open the change and read **Executed by** and **Workflow**. See [Find changes](broken://pages/wrEewxwkqffv0s3nlGci).

</details>

<details>

<summary>A filter doesn't narrow the list on API Calls &#x26; Errors</summary>

**Why:** **All statuses** filters API calls only. **All categories** and **All entity types** filter errors only.

**What to do:** Select **API calls only** or **Errors only** first. See [API Calls & Errors](broken://pages/zju4J3WT3yx3VJ1hCAHF).

</details>

<details>

<summary>An email search finds nothing for an application</summary>

**Why:** Application numbers are matched in the email subject.

**What to do:** Search by the application ID, taken from the application's page address. See [Find emails](broken://pages/t9hQPMOBWYjBP1YQlVr3).

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