mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-27 07:05:51 +00:00
08bbcc4dd7
AMM object: some clarifications AMM references: incomplete draft AMM updates AMM: add AMMBid, clarify more stuff Docs for AMMBid transaction AMM: more work on error codes AMM: example transactions, related upates Fix broken links AMM: reflect naming updates more AMMBid edits Add amm_info API method Add style for AMM label AMM: more clarifications on tx, accounts AMM references: Clean up draft amm_info: reflect code updates AMM: updates for the latest changes AMM: update flags for Deposit/Withdraw AMM: update JSON examples for latest code Serialization: add STIssue type STIssue: clarify definition with commas
34 lines
3.1 KiB
Markdown
34 lines
3.1 KiB
Markdown
---
|
|
html: ter-codes.html
|
|
parent: transaction-results.html
|
|
blurb: ter codes indicate that the transaction failed, but it could apply successfully in the future, usually if some other hypothetical transaction applies first.
|
|
labels:
|
|
- Transaction Sending
|
|
---
|
|
# ter Codes
|
|
|
|
These codes indicate that the transaction failed, but it could apply successfully in the future, usually if some other hypothetical transaction applies first. They have numerical values in the range -99 to -1. The exact code for any given error is subject to change, so don't rely on it.
|
|
|
|
**Caution:** Transactions with `ter` codes are not applied the current ledger and cannot cause any changes to the XRP Ledger state. However, a transaction that provisionally failed may still succeed or fail with a different code after being automatically reapplied. For more information, see [Finality of Results](finality-of-results.html) and [Reliable Transaction Submission](reliable-transaction-submission.html).
|
|
|
|
| Code | Explanation |
|
|
|:-----------------|:----------------------------------------------------------|
|
|
| `terFUNDS_SPENT` | **DEPRECATED.** |
|
|
| `terINSUF_FEE_B` | The account sending the transaction does not have enough XRP to pay the `Fee` specified in the transaction. |
|
|
| `terLAST` | Used internally only. This code should never be returned. |
|
|
| `terNO_ACCOUNT` | The address sending the transaction is not funded in the ledger (yet). |
|
|
| `terNO_AMM` | The AMM-related transaction :not_enabled: specifies an asset pair that does not currently have an AMM instance. |
|
|
| `terNO_AUTH` | The transaction would involve adding currency issued by an account with `lsfRequireAuth` enabled to a trust line that is not authorized. For example, you placed an offer to buy a currency you aren't authorized to hold. |
|
|
| `terNO_LINE` | Used internally only. This code should never be returned. |
|
|
| `terNO_RIPPLE` | Used internally only. This code should never be returned. |
|
|
| `terOWNERS` | The transaction requires that account sending it has a nonzero "owners count", so the transaction cannot succeed. For example, an account cannot enable the [`lsfRequireAuth`](accountset.html#accountset-flags) flag if it has any trust lines or available offers. |
|
|
| `terPRE_SEQ` | The `Sequence` number of the current transaction is higher than the current sequence number of the account sending the transaction. |
|
|
| `terPRE_TICKET` | The transaction attempted to use a [Ticket](tickets.html), but the specified `TicketSequence` number does not exist in the ledger. However, the Ticket could still be created by another transaction. |
|
|
| `terRETRY` | Unspecified retriable error. |
|
|
| `terQUEUED` | The transaction met the load-scaled [transaction cost](transaction-cost.html) but did not meet the open ledger requirement, so the transaction has been queued for a future ledger. |
|
|
|
|
<!--{# common link defs #}-->
|
|
{% include '_snippets/rippled-api-links.md' %}
|
|
{% include '_snippets/tx-type-links.md' %}
|
|
{% include '_snippets/rippled_versions.md' %}
|