ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-20 03:35:51 +00:00
Code Issues Packages Projects Releases Wiki Activity

find/replace all universal error types links

Browse Source
This commit is contained in:
mDuo13
2018-05-11 12:15:00 -07:00
parent d062798429
commit e30fb03a48
52 changed files with 54 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/references/rippled-api/public-rippled-methods/transaction-methods/sign.md
View File

@@ -209,7 +209,7 @@ The response follows the [standard format](#response-formatting), with a success
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
* `highFee` - The current load-based multiplier to the transaction cost exceeds the limit for an automatically-provided transaction cost. Either specify a higher `fee_mult_max` (at least 1000) in the request or manually provide a value in the `Fee` field of the `tx_json`.
* `tooBusy` - The transaction did not include paths, but the server is too busy to do pathfinding right now. Does not occur if you are connected as an admin.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/sign_for.md
View File

@@ -221,7 +221,7 @@ The response follows the [standard format](#response-formatting), with a success
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
* `srcActNotFound` - If the `Account` from the transaction is not a funded address in the ledger.
* `srcActMalformed` - If the signing address (`account` field) from the request is not validly formed.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/submit.md
View File

@@ -271,7 +271,7 @@ The response follows the [standard format](#response-formatting), with a success
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `amendmentBlocked` - The transaction cannot be submitted to the network because the `rippled` server is [amendment blocked](concept-amendments.html#amendment-blocked).
* `highFee` - The `fee_mult_max` parameter was specified, but the server's current fee multiplier exceeds the specified one. (Sign-and-Submit mode only)
* `internalJson` - An internal error occurred when serializing the transaction to JSON. This could be caused by many aspects of the transaction, including a bad signature or some fields being malformed.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/submit_multisigned.md
View File

@@ -244,7 +244,7 @@ The response follows the [standard format](#response-formatting), with a success
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
* `srcActMalformed` - The `Account` field from the `tx_json` was invalid or missing.
* `internal` - An internal error occurred. This includes the case where a signature is not valid for the transaction JSON provided.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/transaction_entry.md
View File

@@ -210,7 +210,7 @@ There are a couple possible reasons the server may fail to find the transaction:
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `fieldNotFoundTransaction` - The `tx_hash` field was omitted from the request
* `notYetImplemented` - A ledger version was not specified in the request.
* `lgrNotFound` - The ledger specified by the `ledger_hash` or `ledger_index` does not exist, or it does exist but the server does not have it.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/tx.md
View File

@@ -199,7 +199,7 @@ The response follows the [standard format](#response-formatting), with a success
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
* `txnNotFound` - Either the transaction does not exist, or it was part of an older ledger version that `rippled` does not have available.

2
content/references/rippled-api/public-rippled-methods/transaction-methods/tx_history.md
View File

@@ -889,7 +889,7 @@ The fields included in each transaction object vary slightly depending on the ty
## Possible Errors
* Any of the [universal error types](#universal-errors).
* Any of the [universal error types][].
* `invalidParams` - One or more fields are specified incorrectly, or one or more required fields are missing.
* `noPermission` - The `start` field specified was greater than 10000, but you are not connected to the server as an admin.