When a transaction is prepared in the Ripple Custody UI, the system automatically executes a dry-run of the operation. As a result, if an anomaly impacts the indexers or (blockchain) nodes, you may encounter errors.
Note
Ripple can't prevent these types of errors because they usually happen when you make updates to a component.
The following table gives you an overview of these errors, their root causes, and consequences. However, this list isn't exhaustive and doesn't list all possible errors.
| Error message | Possible root cause | Consequence |
|---|---|---|
Payload has validation issues preventing the execution of the dry-run, refer to the errors list for more details | You can't broadcast a transaction because the system can neither prepare nor detect transactions. The accounts' balance may differ from the on-chain balance. | |
Tracker identification failed | The indexer is unable to establish a connection to the node. | You can't broadcast a transaction because of the missing connection between the indexer and the node; no accounting operation (such as transactions, balances, address generation) will be performed. |
Tracker not in sync | The indexer was unavailable for a period of time. | You can still broadcast a transaction, but a delay in the detection of both inbound and outbound transactions, which impacts the accounts' balance, is expected. |
Tracker not in sync | The node was unavailable for a period of time. | Depending on the ledger, you can still broadcast a transaction, but a delay in the detection of both inbound and outbound transactions, which impacts the accounts' balance, is expected. |
Tip
If you run into an error where the indexer and node are out of sync, Ripple recommends that you don't broadcast a transaction. However, if you must make an urgent transaction, make sure you manually verify the transaction.