> 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/transaction-has-been-processed-already.md).

# Transaction has been processed already

{% hint style="danger" %}
`Error processing request: Transaction Error: Request rejected; the transaction has been processed already`
{% endhint %}

This error occurs because the request sent to Unifi references a transaction that is either complete, errored or timed out. The reason for this is to prevent systems from spamming Unifi with repeat requests using the same ID.

If you are sending a receipt message, then this is likely to occur because the transaction in the receiving system is in an invalid state. Check the state of the receiving transaction, it should be in the awaiting receipt state, otherwise:

* If it is complete, then a previous request has completed it, and you must be sending duplicate receipts.
* If it is errored, then find out why and resolve. Your receipt will then process correctly.
* If it is timed out, then ensure you send the receipt in a timely fashion, or update the receiving systems integration settings to increase the time to wait for receiving receipt messages.


---

# 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/transaction-has-been-processed-already.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.