#chad_error

1 messages · Page 1 of 1 (latest)

glacial cradleBOT
#

👋 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/1404514417185521755

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

mild whale
#

Can you share request IDs

jaunty blaze
#

Attempting to gather those

mild whale
#

Ok

jaunty blaze
#

Would that be the id you're after?

#

or any of the payment intents below?

mild whale
#

Can you provide both?

jaunty blaze
#

Does the SS above work for the Ids or do you need them copied/pasted in here?

mild whale
#

I need them copied and pasted here.

jaunty blaze
#

We're trying to figure out if we can export out of DT

mild whale
#

I was able to obtain the PaymentIntent from the 1st screenshot you shared. There doesn't appear to be an error. Payment was made susccessfully.

jaunty blaze
mild whale
#

I'm referring to pi_3RuzD2REZosXeg8o1aGY4TFQ

jaunty blaze
#

So it it possible that the first attempt to process the payment for that intent failed...they retried and it went through?

#

This was ongoing for 39 minutes:

image.png
#

that's Mountain time

mild whale
jaunty blaze
#

In a scenario like that, is it possible to see if any failures occured attached to that PI?

#

Any reason why we would have been getting 503's during that timeframe? Any maintenance or other issues that could have caused it you're aware of?

mild whale
#

There were no failures for pi_3RuzD2REZosXeg8o1aGY4TFQ

#

You mentioned Mountain time, where are you exacly?

jaunty blaze
#

I'm in Billings, Montana at Headquarters for KOA, however our campgrounds that were seeing issues are all over the US

#

There are also reports in downdetector during the same window

image.png
mild whale
#

I believe someone reached out on Friday from Kampgrounds of America about a similar issue. I'm going to doublecheck on my end.

jaunty blaze
#

Appears there was a significant slowdown prior to the errors as well

#

We were seeing issues on Friday as well, but I don't know that this is related. On Friday, only the campgrounds in the SLC/Idaho areas were impacted due to a Google Fiber line being down in SLC. That doesn't appear to be the case today.

mild whale
#

Let me reach out internally.

austere bluff
#

Hello, looking in to this. Do you know if these issues are still ongoing and if not do you know when the last one of these errors happened for you?

jaunty blaze
#

Hi @austere bluff , this was ongoing between 10:43 - 11:17 Mountain time

#

11:17 was the last one we saw

#

Not sure if this is related...but maybe?

austere bluff
#

Gotcha, I found the internal issue that caused that and 17:17 UTC (11:17 MT) is when we said that should have been fully resolved. It looks like this was a separate issue to the one on Friday, though it does have a similar shape in the end for you where something upstream caused our API to be unreachable in AZ for some users. So let us know if you receive any other reports and I can escalate them.

jaunty blaze
#

Are there any details on the root cause so I can relay them to our leadership team? They are hoping for a Root Cause analysis from me 🙂

austere bluff
#

Not immediately seeing detail that I can share but am asking now. Also my apologies but I was a bit mistaken, the impact was to an "Availability Zone" (AZ) not to Arizona. I was reading too fast there, but the other details do still line up.

jaunty blaze
#

Thank you for clarifying, I was thinking Arizona 🙂

glacial cradleBOT