REPLY_TIMEOUT: Action timed out

jrandeniya commented 3 years ago

We have started to see "REPLY_TIMEOUT: Action timed out" errors when using the drop-in ChargeBee Javascript V2 and the React wrapper for it. These errors happen intermittently.

We did a bit of digging into the ChargeBee SDK and found that the issue was in the ReplyMessage.ts file. The constructor establishes a self destruct with a timeout of 10,000ms and expects the caller to call markAsReceived method before the timeout expires. However, due to some unknown issue this callback is never called and the REPLY TIMEOUT error is thrown.

This is a critical issue for our users because the CB iFrame fails to load and our users cannot enter their credit card details.

We saw this issue ~40 times/week with v0.2.0 but it spiked to 103 events in a single day when we upgraded to v0.4.0. We will monitor for another 24 hours and if issues persist, we will roll back the upgrade.

Can you please advise?

cb-dinesh commented 3 years ago

Hi @jrandeniya, Do you still see this issue happening?

eek commented 3 years ago

We also experience this error.

In the past 14 days, it happened 7.5k times for 2.1k users

Past 24h happened around 100 times:

(I guess CBError is your function)

We also see other errors:

Loading chunk 27 failed. (error: https://js.chargebee.com/v2/27-5a1ceb90e75f6ed5571a.js)

339 events for 54 users (past 14 days)

MattHoneycutt commented 3 years ago

We're seeing this pretty frequently, too, with the Angular wrapper.

cb-dinesh commented 3 years ago

Hi there! This error is not specific to wrapper, rather its coming from Chargebee.js. We are actively looking into minimising the REPLY_TIMEOUT errors. For 99% of the cases, this error does not impact the workflow.

I'll keep this thread updated on the details.

ashleyoldershaw commented 2 years ago

Just to confirm this is happening with us as well -

It seems to be happening when users interact with the page and it refreshes the wrapper a lot, although I can't find a simple cause - if you want me to show you I can sort something out

Thanks

ciriousjoker commented 2 years ago

Happens for us too, although so far it only happened when the loading of the site is impaired due to "fake breakpoints" that aren't actually hit but which cause the browser to delay the calls by 100ms or so.

cb-dinesh commented 2 years ago

Hi All, Yes I can acknowledge this issue. It is coming from Chargebee.js which has iframe implementation. During component refresh, the iframes gets unmouted leading to these errors in the console. We are already working on a fix, will keep this thread posted on the ETA.