Skip to content

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

Closed
konstantinabl opened this issue Oct 17, 2024 · 4 comments
Assignees
Labels
bug Something isn't working
Milestone

Comments

@konstantinabl
Copy link
Contributor

konstantinabl commented Oct 17, 2024

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

@Nana-EC
Copy link
Contributor

Nana-EC commented Nov 11, 2024

@konstantinabl can we connect the sdk bug here?

@quiet-node quiet-node modified the milestones: 0.59.0, 0.61.0 Nov 11, 2024
@quiet-node quiet-node modified the milestones: 0.61.0, 0.62.0 Nov 26, 2024
@quiet-node quiet-node modified the milestones: 0.62.0, 0.63.0 Dec 11, 2024
@quiet-node
Copy link
Contributor

@konstantinabl Was this got resolved?

@quiet-node quiet-node modified the milestones: 0.63.0, 0.64.0 Dec 26, 2024
@Nana-EC
Copy link
Contributor

Nana-EC commented Jan 13, 2025

@konstantinabl let's get a few logs for instances of transactions and pass it on to services team for investigations.
With the workaround this is less of a bug but we still want to close this off

@quiet-node quiet-node modified the milestones: 0.64.0, 0.65.0 Jan 15, 2025
@quiet-node quiet-node modified the milestones: 0.65.0, 0.66.0 Jan 29, 2025
@quiet-node quiet-node modified the milestones: 0.66.0, 0.67.0 Feb 12, 2025
@konstantinabl
Copy link
Contributor Author

As far as I understand services team says this is expected behaviour, so Im closing the issue
@Nana-EC @Ferparishuertas

@github-project-automation github-project-automation bot moved this from Blocked to Done in Smart Contract Sprint Board Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
3 participants