#morenomdz_webhooks

1 messages ¡ Page 1 of 1 (latest)

sharp solsticeBOT
#

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

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

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.

haughty fable
#

We have a new project that is going to try to fully automate the reconciliation when failed payouts happen so we can properly track in our system. What we need to know if we can fully trace back a failed payout, to all its previous "attempts" (previous failed payouts, standard or instant). We tried this before and we never had enough data to do so.

sharp solsticeBOT
tawny kayak
#

Hi! Can you share an ID related to this issue?

sharp solsticeBOT
haughty fable
#

one sec

#

before I get back an id from the team, can you confirm if we can trace back a failed payout to previous attempts?

#

For example, this account

acct_1R8OypFShQkpf10M

his payouts have been failing back and forth, has a mix of standard and instance payouts, and it is very hard for us to reconcile on our side which transfers were tried to be paid on which payouts

storm gazelle
#

fyi i'm taking over the thread for timebox. i don't think that's possible directly from the payout object though, there isn't a field that would provide that kind of information. let me poke around at some things though

haughty fable
#

lets say the latest, po po_1RnYsZFShQkpf10MbLrB9xpc, can we trace back all the way back to the original transfers that may have happened weeks ago

storm gazelle
#

the closest thing i could think of off the top of my head would just be to list all payouts and then dig through those to try to piece together the story on your end. but as far as i know we don't explicitly link payouts to previous attempts, they're all stand-alone.

haughty fable
#

yea I think we might have to do that,

#

are we sure there is no data in the metadata for example?

storm gazelle
#

metadata is set by you as the owner of an integration, so if you're creating manual payouts you can add whatever information you want there

#

but we don't set metadata by default

haughty fable
#

Got it so the standard payout won't have it, but our instant payouts could have whatever metadata we add? Or is there a way for us to also configure what sort of metadata we are sending in standard payouts

storm gazelle
#

our instant payouts could have whatever metadata we add
yep!

is there a way for us to also configure what sort of metadata we are sending in standard payouts
i am fairly certain that this is not possible

haughty fable
#

any way we could confirm that? My intuition says it is not possible either, we just want to confirm there is no off the shelf route for us to trace this

storm gazelle
#

it might be worth checking with our regular support team, they work a lot more with production users and generally know more about the ins and outs of standard payouts than we do

#

let me double check one thing real quick

haughty fable
#

kk

storm gazelle
haughty fable
#

gotcha

#

I think we have the info we need, thanks