2

"tx_bad_seq" occurs when the transactions sequence number isn't exactly tx source accounts current sequence number + 1. When a transaction gets submitted successfully the sequence number is consumed and you'll need to calculate (or fetch) the next one. The SDKs normally do that for you with server.loadAccount(). So why does it fail in your case ...


1

If you've gotten back a tx_bad_seq, that transaction is fully failed. The node does not cache or store that transaction. It will have to be re-submitted once the sequence number is correct. There is one special case to this. If your account sequence is S, and you submit S+2, the Horizon HTTP API will wait for up to 30s before responding. If S+1 is received ...


Only top voted, non community-wiki answers of a minimum length are eligible