#callmarl-list-payout

1 messages · Page 1 of 1 (latest)

marsh dew
#

Hi 👋 that request does look structured correctly to retrieve pending payouts, taking a closer look.

remote totem
#

Yes it's strange, because the returned value is paid. In this test the destination doesn't have any pending payout.

marsh dew
#

My suspicion is that we're more lenient with the pending status in test mode since payouts immediately succeed there and don't sit in a pending state at all.

#

Do you see the same behavior if you filter for failed?

remote totem
#

I will check

#

It work filtering on failed no data is returned

{
  "data": [],
  "has_more": false,
  "object": "list",
  "url": "/v1/payouts"
}
marsh dew
#

Sorry, was trying to find some payouts in one of my test accounts so I could try to replicate, but when I filter for pending I'm not getting any results. How quickly after triggering the payout did you make the first list request?

remote totem
#

Let me check the log

marsh dew
#

Sorry, but I've got to step into a meeting, my teammate @quasi mulch can continue helping with this. 👋

remote totem
#

First time (3:16:12 PM) trying to retrieve pending at (3:32:08 PM)
An other test with other account at (3:52:41 PM) trying to retrieve pending at (3:53:26 PM)

remote totem
quasi mulch
#

Thank you for your patience. I am looking at other threads and hope to get to this one in a couple minutes.

remote totem
proper patrol
#

@remote totem this looks like a bug to me too. Unfortunately the whole pending -> succeeded transition in Test mode is not great since it's all near instant and I think it's making the API confused.

My advice though is to ignore the pending status entirely, there shouldn't be a need for you to list payouts with that specific status, they are sequential/ordered and I'd just list Payouts really. I'll still flag internally but it's not something we'd fix quickly

remote totem
#

Ok I will manage differently thanks a lot for your help.