Error processing request: Transaction Error: Request rejected; the transaction has been processed already
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.
Initiating transaction not found for inbound receipt
This error is usually the result of domain separation. The inbound integration user is in a domain that does not have visibility of the domain that the transaction was created in. Check the domain of the transaction (this will be the same as the ticket being integrated) and compare to the domain on the received HTTP Request (this is the domain of the integration user).
Loading...
Message ID not found; it is expected in a receipt
For Unifi to identify what transaction an inbound receipt is for, it needs to locate the message IDs from the inbound request. These IDs are then cross referenced against the Message ID and External Message ID fields on the transaction to make a match. These values are extracted from the request using the Reference lookup script found on the inbound settings of a Receipt message.
This error signifies that Unifi could not find a value for the message ID from the received request, and indicates that the issue is either with the received request, i.e. no message ID given, wrong format, etc or the reference lookup script for this message is incorrect.
Message is not valid for this bond
This error occurs because the bond state for the transaction being sent is in a state which does not match the state specified on the message definition.
Usually occurs when a bond has been closed and an external system attempts to send an update, which requires the bond to be open.
Check the bond state against that of the message definition and decide whether the definition needs to be amended, or the sending system needs to change its ways.
Loading...
Loading...