waitForTransactionReceipt timeout exception after confirmed

[vimtor]

Check existing issues

• I checked there isn't already an issue for the bug I encountered.

Viem Version

2.13.1

Current Behavior

Sometimes, when calling waitForTransactionReceipt with a timeout, the call times out, but when you check the transaction hash on an explorer, you can see that the transaction was confirmed within the timeout period.

We are experiecing this on Taiko's chain. Here are our server logs:

And here is the transaction on the explorer:

As you can see, the transaction was confirmed in a minute, but the client wasn't able to find it after 5 minutes.

Expected Behavior

waitForTransactionReceipt should only throw if the transaction is not confirmed within the timeout period.

Steps To Reproduce

I can't provide an exact reproduction since I don't know the origin of the issue.

Link to Minimal Reproducible Example

No response

Anything else?

No response

[github-actions]

Hello @vimtor.

Please provide a minimal reproduction using StackBlitz, TypeScript Playground (for type issues), or a separate minimal GitHub repository.

Minimal reproductions are required as they save us a lot of time reproducing your config/environment and issue, and allow us to help you faster.

Once a minimal reproduction is added, a team member will confirm it works, then re-open the issue.

[tmm]

Are you using a public RPC URL or a paid service? Public RPCs tend to not be as high-availability/responsive.

[vimtor]

Are you using a public RPC URL or a paid service? Public RPCs tend to not be as high-availability/responsive.

We are using a private RPC, wouldn't it give a different error instead?

[jxom]

As you can see, the transaction was confirmed in a minute, but the client wasn't able to find it after 5 minutes.

Viem’s Client is only as smart as the RPC Provider that you pass to it (via http Transport). Viem periodically calls the RPC Provider to try and retrieve the receipt. If no receipt is resolved from the RPC Provider from these calls, then Viem throws the error that you see here.

Have you tried using an alternate RPC Provider?

[github-actions]

This issue has been locked since it has been closed for more than 14 days.

If you found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest Viem version. If you have any questions or comments you can create a new discussion thread.