Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

document ShardCongested error on tx submission #2018

Merged
merged 1 commit into from
Jun 4, 2024
Merged

document ShardCongested error on tx submission #2018

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/5.api/rpc/transactions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
Expand All @@ -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>
Expand Down Expand Up @@ -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>
Expand All @@ -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>
Expand Down
Loading