Tangany is continuously improving the reliability of the asynchronous processes in the Custody API to enhance the reliability of our transaction APIs and eliminate future causes of mid-flight failing transaction request processes. In rare cases, transactions may not be complete with a successful status. Please consult the following API documentation article to understand statuses of asynchronous operations (e.g. transactions): https://docs.tangany.com/docs/tangany-custody-api/ay1339exoa0xd-concepts#asynchronous-operations
Below is a list of possible error messages of a failed background process despite a successful transmission of a blockchain transaction
- Failed due to unexpected application behavior
- Timeout value of xx:xx:xx was exceeded by function: Functions.DA_get-tx-status
- Timed out polling for block inclusion. Transaction was possibly lost, overridden or blocked by a previous transaction
- Activity function 'DA_get-tx-status' failed: method handler crashed
The general advice is if a transaction error contains the property "txHash", then the transaction was successfully submitted to the blockchain and should not be retried.
This article https://docs.tangany.com/docs/tangany-custody-api/4faa17326caad-errors#retry-handling provides a guideline on identifying the blockchain transmission status of Custody API transactions for crashed/failed async request statuses. It further clarifies the decision process of resubmitting transactions and prevents instances of redundant asset spending.