From c307526bedf9faa7b6c3a23c8303d25aec9e2a29 Mon Sep 17 00:00:00 2001
From: Jakob Meier <mail@jakobmeier.ch>
Date: Tue, 4 Jun 2024 13:39:07 +0200
Subject: [PATCH] document `ShardCongested` error on tx submission

---
 docs/5.api/rpc/transactions.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/5.api/rpc/transactions.md b/docs/5.api/rpc/transactions.md
index 68f2c2b62f7..f3822880aef 100644
--- a/docs/5.api/rpc/transactions.md
+++ b/docs/5.api/rpc/transactions.md
@@ -192,6 +192,7 @@ Here is the exhaustive list of the error variants that can be returned by `broad
       <td>
         <ul>
           <li>See <code>error.cause.info</code> for details</li>
+          <li>If <code>error.cause.info</code> is <code>ShardCongested</code></li>, resubmit the identical transaction. (Consider adding a priority fee once [NEP-541](https://github.com/near/NEPs/pull/541) is released.)
         </ul>
       </td>
     </tr>
@@ -200,7 +201,7 @@ Here is the exhaustive list of the error variants that can be returned by `broad
       <td>Transaction was routed, but has not been recorded on chain in 10 seconds.</td>
       <td>
         <ul>
-          <li> Re-submit the request with the identical transaction (in NEAR Protocol unique transactions apply exactly once, so if the previously sent transaction gets applied, this request will just return the known result, otherwise, it will route the transaction to the chain once again)</li>
+          <li> Resubmit the request with the identical transaction (in NEAR Protocol unique transactions apply exactly once, so if the previously sent transaction gets applied, this request will just return the known result, otherwise, it will route the transaction to the chain once again)</li>
           <li>Check that your transaction is valid</li>
           <li>Check that the signer account id has enough tokens to cover the transaction fees (keep in mind that some tokens on each account are locked to cover the storage cost)</li>
         </ul>
@@ -1313,6 +1314,7 @@ Here is the exhaustive list of the error variants that can be returned by `broad
       <td>
         <ul>
           <li>See <code>error.cause.info</code> for details</li>
+          <li>If <code>error.cause.info</code> is <code>ShardCongested</code></li>, resubmit the identical transaction. (Consider adding a priority fee once [NEP-541](https://github.com/near/NEPs/pull/541) is released.)
         </ul>
       </td>
     </tr>
@@ -1321,7 +1323,7 @@ Here is the exhaustive list of the error variants that can be returned by `broad
       <td>Transaction was routed, but has not been recorded on chain in 10 seconds.</td>
       <td>
         <ul>
-          <li> Re-submit the request with the identical transaction (in NEAR Protocol unique transactions apply exactly once, so if the previously sent transaction gets applied, this request will just return the known result, otherwise, it will route the transaction to the chain once again)</li>
+          <li> Resubmit the request with the identical transaction (in NEAR Protocol unique transactions apply exactly once, so if the previously sent transaction gets applied, this request will just return the known result, otherwise, it will route the transaction to the chain once again)</li>
           <li>Check that your transaction is valid</li>
           <li>Check that the signer account id has enough tokens to cover the transaction fees (keep in mind that some tokens on each account are locked to cover the storage cost)</li>
         </ul>