Overview
The purpose of this guide is to assist operators in understanding the system for failed transactions in MG+.
This system is in place to inform the agent of the current state of failed transactions on the MG+ system. It is then the responsibility of the agent to adjust the transaction on their system according to the failed state, and mark the transaction as resolved on the MG+ system.
Several events can cause a failed transaction to occur, for example:
-
Agent API error
-
Timeout to the Agent API
-
Other network or software related issues
Version Information
|
Version |
Content |
Publish Date |
|
1.0.0 |
MG+ Failed Transactions Quick Guide published. |
|
|
1.0.1 |
Fixed the description regarding the Agent action. |
|
|
1.1.0 |
Grammatical and formatting updates. |
|
|
1.2.0 |
Updated the descriptions for the “Obtain a List of Failed Transactions in the System” and “Marking a Failed Transaction As Resolved” API methods. |
|
|
1.3.0 |
Added Failed Transactions section. |
|
|
1.3.1 |
Updated Failed Transactions Automatic Retry Mechanism intervals. |
|
|
1.3.2 |
Conversion from Traditional Chinese into Simplified Chinese. |
|
|
1.3.3 |
Updated the “Obtain a List of Failed Transactions in the System” response example. |
|
|
1.3.4 |
Updated “Failed Transactions” content and pages. Updated “API Response Comparison Example”. |