4

I was getting this error when sending a transaction to the RPC:

Transaction failed: RPC response error -32005: Node is behind by 166 slots

Why does this happen?
How should we react to this error? Shall we simply retry after a delay?

2
  • "react" in what role? are you the node operator or simply querying it as a dev?
    – trent.sol
    Commented Aug 2, 2022 at 0:36
  • Querying it as a dev
    – itsfarseen
    Commented Aug 2, 2022 at 7:24

2 Answers 2

5

This means the RPC node you are using can't keep up with leader for some reason (network, load surge, etc).

You can't do anything about it, just wait until it catches up, or use another RPC to send your request.

1
2

@vladyslav-melnychenko's answer is correct with regard to cause. However if you know you're using a load-balanced RPC endpoint, it is typically okay to retry the operation at a reasonable rate until it succeeds. The delinquent backend will either catch up or be removed from the pool. Keep in mind that if you've already successfully queried some time-sensitive information, like a recent blockhash, you may need to retry operations besides the one that actually failed as well

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.