> For the complete documentation index, see [llms.txt](https://docs.sharelogic.com/unifi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md).

# No retry for requests with 401 response

When an outbound HTTP Request fails with a 401 error, it means the request was unauthorised by the other system - i.e. the authentication credentials given were invalid.

Unifi has a default Response Action for 401 responses which prevents retries for requests that fail with this error. Since credential issues can only be fixed by someone modifying them, retries would continue to use the same invalid authentication and continue to fail.

When a Response Action is applied to an outbound HTTP Request, it is marked on the record so you can easily see how it was handled.

<figure><img src="/files/R23t3P6gTNgsVdbL1BgW" alt=""><figcaption><p>Response Action applied to HTTP Request</p></figcaption></figure>

### Workaround

If for some reason you want to retry requests that fail with a 401 error, you can create a new 401 Response Action for the Integration (and specific Message if necessary) and enable retry. This will override the default Unifi 401 Response Action.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sharelogic.com/unifi/troubleshooting/integration-responses/no-retry-for-requests-with-401-response.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.