-
Notifications
You must be signed in to change notification settings - Fork 126
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.
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
transaction was not confirmed in a given deadline, but it may still be confirmed later #291
Comments
Hi, externals may lost during broadcasting between liteserver and nodes sometimes, increasing limit will not help i think, you better to wait for timeout and message timeout (specified in wallet) and retry in this case. |
The problem is I got "transaction was not confirmed in a given deadline, but it may still be confirmed later", for both successful transactions and failed transaction and I have no idea how I can fix it. I set more than 20s sleep between each transaction but still I got this error. Sometimes too much. |
the only way that I found to solve that was something like: |
Won't work for me as I send transactions the to same address (imagine DstAddr is always XYZ), so there's no unique factor that I can check that the specific transaction to XYZ address is received or not. |
Hi! Hope you are doing well.
I have a big problem with
Do you think increasing the scanning number from 5 to maybe 10 can fix this problem? I am sending transactions with a normal sleep time like 15s or sometimes 20s. But still sometimes I get this error. It's really make the system unreliable because sometimes it does not send the transactions, and sometimes it sends.
tonutils-go/ton/sendmessagewait.go
Line 78 in 642950d
Do you have any idea?
The text was updated successfully, but these errors were encountered: