-
Notifications
You must be signed in to change notification settings - Fork 81
Getting timeout exceeded in the sdk client even when transaction is submitted #3118
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
Comments
This was referenced Oct 21, 2024
@konstantinabl can we connect the sdk bug here? |
@konstantinabl Was this got resolved? |
@konstantinabl let's get a few logs for instances of transactions and pass it on to services team for investigations. |
As far as I understand services team says this is expected behaviour, so Im closing the issue |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
It has been noticed that an 'SDK timeout exceeded' error appears sporadically in our CI, but also on mainnet. The transaction is actually passed to the consensus node, but we get a null value from the SDK thus it is assumed the transaction is not submitted.
Steps to reproduce
Currently, not easily reproducable.
CI logs - https://github.com/hashgraph/hedera-json-rpc-relay/actions/runs/11142264400/job/30964850632
Mainnet logs - https://production.grafana.hedera-ops.com/goto/5H7WN0kNR?orgId=1
Additional context
SDK Issue - hiero-ledger/hiero-sdk-js#2614
No response
Hedera network
mainnet
Version
0.57
Operating system
None
The text was updated successfully, but these errors were encountered: