#foobarrio-radar-feature
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- foobarrio-radar-feature, 13 hours ago, 42 messages
Hello! Do you have a more recent request ID I can take a look at?
Hi Karbi. I don't have a request ID, I just saw this in our application logs. Did you see my thread from last night?
Yup, I saw it! A request ID will help me pinpoint whether this is a recurrence of the same issue, or if it's because they're using the older version of stripe.js that had the bug and was cached
It seems like it was just 1 person who may have had a stale session
foobarrio-radar-feature
Yeah, that would be my guess as well - since you're only seeing it once it's more likely to be a stale session
Right. My concern was it fired twice, but it was the same user. I think we're ok here. Appreciate your quick response
happy to help! If you see a sudden spike in this error happening again definitely let us know