#martin-gaibisso_error

1 messages ¡ Page 1 of 1 (latest)

unkempt heraldBOT
#

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

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

tiny sedge
#

Hello

#

Do you have a request ID of an error you are seeing?

dull gazelle
#

nothing changed our end and suddenly metadata is arriving as this:{
"metadata": {
"Account": {
"ID":
"acct_1MsjH7QtUa71jsTy"
Connected account
,
},
"Brippo": {
"UID":
"op_68825eb0798f7",
},
"Customer": {
"Email":
"chloelouisesewell@gmail.com",
},
"Extension": {
"Signature":
"Core 100.4.6, Frontend 100.4.7",
},
"Fee": {
"Category":
"Domestic card",
"Rate":
"0.014000",
},
"IP": {
"Address":
"2a02:c7c:84e7:b900:d884:66

#

requests are failing

tiny sedge
#

Yeah sorry that is an update to a Charge and the request is made using your secret API key from your server (using our Node SDK) so something did change on your end.

#

This is the data that you are passing us -- we don't populate your request body for you.

dull gazelle
#

nothing changed our end

#

is it possible something changed in your data processing?

tiny sedge
#

Are you saying that you previously passed metadata this exact same way and you didn't receive an error? Becuase that wouldn't be the case as metadata doesn't accept objects/hashes, only key/value pairs.

dull gazelle
#

some requests are going through tho

tiny sedge
#

It sounds like you are saying the literally POST body data has changed.

#

You are now seeing different data in your POST body, correct?

dull gazelle
#

yeah, what i see in our dashboard requests

#

the metadata shows like that and causes an error

#

but nothing changed our end

tiny sedge
dull gazelle
#

its the same system

tiny sedge
#

This data is passed from your server, so while I know currently think nothing changed on your end, that isn't the case.

dull gazelle
#

sending these

#

some fail and some dont

#

we send the same requests

tiny sedge
#

You need to go back and debug on your side -- we just receive this data, we don't do anything to it on our end.

#

So next step is likely to add logging on your end if you aren't sure why you are passing a hash instead of key/value pair.

dull gazelle
#

i see the problem

#

you are managing keys differently

#

the ones with a space in the middle are failing

tiny sedge
#

Okay I'm looking, one moment.

dull gazelle
#

"Order": {
"ID":
"FD75615326",
},
"Provider":
"Apple Pay",

#

"Order ID" should be the key

#

Provider is fine

#

i can assure you nothing changed our end

tiny sedge
#

Okay I'lm investigating, apologies for jumping to conclusions.

#

Give me a few minutes.

dull gazelle
#

no worries

tiny sedge
#

Okay this is a bug on our end and we are working on it with priority. Thanks so much for reporting.

dull gazelle
#

ok, thanks for the update

#

ETA?

tiny sedge
#

Not sure yet, we are still investiating.

#

Okay things should be resolved now.

dull gazelle
#

i can see

tiny sedge
#

Yep please do check. We aren't seeing errors on our end anymore (nor do I see any over the last several minutes in your logs)

dull gazelle
#

any details about the incident?

tiny sedge
#

Unfortunately I don't have any details beyond it being a bug on our end that was resolved. If you want more details then you can contact our Support team via https://support.stripe.com/contact/login and they can follow up with you after the root cause is determined.

unkempt heraldBOT