#val_unexpected

1 messages ¡ Page 1 of 1 (latest)

foggy violetBOT
#

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

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

hallow patrol
#

Here's an intent id where it happened: pi_3PZEwYGPobLlhSMZ0zqH6g5c

wanton bobcat
#

I still see metadata on that payment intent

#

Oh is it only happening on the Charge object?

#

Do you have a more recent example? Those events are past the 30 day retention

hallow patrol
#

yes, here is one pi_3Pg1boGPobLlhSMZ1x3bireA

#

yes, the metadata stays on the intent but I need it on the charge for some bookkeeping automation I have when the payout is made

#

here's an example of a more recent Revolut charge where that didn't happen: pi_3PcmVxGPobLlhSMZ1i0wdQN8

wanton bobcat
hallow patrol
#

oh yeah you're right actually!

#

It was never set

#

but i don't understand why, the charge usually gets the metadata from the intent when created

#

why in this case did that not happen?

wanton bobcat
wanton bobcat
hallow patrol
#

thank you. will wait

hallow patrol
#

any update?

wanton bobcat
#

Yeah seems to be a bug

#

We'll report the issue

#

Not sure when it'll be resolved, but we'll get it reported

hallow patrol
#

thank you, good to know it's not me going crazy. For now I think I'll solve it by inspecting the metadata in the charge.succeeded block and if it's empty just set it again to the intent one

wanton bobcat
#

yep that's a good workaround for now