#kevin_error
iron zenithBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1458415243926437963
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
vapid lintel
hey there 👋 can you confirm at what step this error happens?
prisma rapids
Hey 😄
Since I wrapped my payment step around a try / catch
I'm not sure either this happen during await elements.submit(); or during await stripe.confirmSetup / await stripe.confirmPayment
The stack trace is not specifying it
Another thing that I can think of is that we currently have A/B test with :
- Version A : Card Element
- Version B : Payment Element
So maybe the error is from Card Element and NVM you can close my thread 😄
vapid lintel
no worries! I'm investigating this internally so will come back to you soon
prisma rapids
Thank yoooou
vapid lintel
so, for the first error ("frame window is not ready"), it's one that we only see a very small number of times per week and we suspect that it's caused by browser extensions - generally the payment can still be completed
for the second one ("Could not retrieve elements store due to unexpected error"), this happens when happens when the API call to fetch the elements session fails (e.g. due to a network/server error)
this is generally a secondary error - the primary issue is the earlier Elements session fetch failure
these are both generally seen as non-fatal errors (i.e. they don't block the payment from being completed)
have you seen any instances where customers were blocked from paying due to these errors?
prisma rapids
On our side, we don't have recording or anything like this so I don't know if the small amount of users were blocked TBH, thanks for the info, it helped me 🙏
vapid lintel
ok cool! it should be safe to treat these as transient and non-fatal, but if you come across any specific instances where the customer was blocked please let us know
prisma rapids
Thank you 😄 Will do!