From 70291c028e8d04c4b5592e3137dc7ffc6667dc8c Mon Sep 17 00:00:00 2001
From: mDuo13 <mduo13@gmail.com>
Date: Thu, 2 Jun 2016 13:25:17 -0700
Subject: [PATCH] tx format - add terQUEUED

---
 content/reference-transaction-format.md | 3 ++-
 reference-transaction-format.html       | 6 +++++-
 2 files changed, 7 insertions(+), 2 deletions(-)

diff --git a/content/reference-transaction-format.md b/content/reference-transaction-format.md
index 0ab64a6a14..3e6f65bdef 100644
--- a/content/reference-transaction-format.md
+++ b/content/reference-transaction-format.md
@@ -1121,7 +1121,7 @@ These codes indicate that the transaction failed and was not included in a ledge
 
 ### ter Codes ###
 
-These codes indicate that the transaction failed, but it could apply successfully if some other transaction was applied 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.
+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.
 
 | Code | Explanation |
 |------|-------------|
@@ -1135,6 +1135,7 @@ These codes indicate that the transaction failed, but it could apply successfull
 | 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-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. |
 | terRETRY | Unspecified retriable error. |
+| terQUEUED | The transaction met the load-scaled [transaction cost](concept-transaction-cost.html) but did not meet the open ledger requirement, so the transaction has been queued for a future ledger. |
 
 ### tes Success ###
 
diff --git a/reference-transaction-format.html b/reference-transaction-format.html
index 1dcc33a795..206b927a11 100644
--- a/reference-transaction-format.html
+++ b/reference-transaction-format.html
@@ -1974,7 +1974,7 @@
 </tbody>
 </table>
 <h3 id="ter-codes">ter Codes</h3>
-<p>These codes indicate that the transaction failed, but it could apply successfully if some other transaction was applied 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.</p>
+<p>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.</p>
 <table>
 <thead>
 <tr>
@@ -2023,6 +2023,10 @@
 <td>terRETRY</td>
 <td>Unspecified retriable error.</td>
 </tr>
+<tr>
+<td>terQUEUED</td>
+<td>The transaction met the load-scaled <a href="concept-transaction-cost.html">transaction cost</a> but did not meet the open ledger requirement, so the transaction has been queued for a future ledger.</td>
+</tr>
 </tbody>
 </table>
 <h3 id="tes-success">tes Success</h3>