#nickdnk

1 messages · Page 1 of 1 (latest)

quick tundraBOT
#

Hello! We'll be with you shortly. 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.

azure forge
#

Hello

#

Do you have an example request ID I can look at?

nova wing
#

Stand by

#

req_mzzfhxfsXprS1e

azure forge
#

Thanks looking

#

I'm surprised that you aren't seeing this happen on other accounts, though maybe this just has to do with the Finland payout rails being faster so the payout actually lands same-day instead of the next day. Do you have a successful retrieval request I can look at from another account?

#

Mostly I think you just will want to retry the following day if you hit this error.

#

There isn't really a better webhook.

nova wing
#

I don't have any code that can reschedule events for 12 hours late

#

It's simply not a concept I work with, I use webhooks for everything stripe related

#

The request browser will only show me errors

#

shouldn't this give me all requests for this endpoint? The only filter is the path

#

But it still only lists errors

azure forge
#

I found a few actually

#

One sec

nova wing
#

There should be plenty, it runs all the time

#

A "report data ready" webhook for a payout would be really helpful here

#

or a payout.updated with report_data_available: true or report_data_available_after: <unix> on the payout object or something?

#

I can add up to 15 minutes of delay to an event via AWS SQS, but that won't be enough in this case

#

I guess the timestamp wouldn't solve my problem though

azure forge
#

Do you know if this is the only account on a rolling weekly payout?

nova wing
#

No, it varies

#

We have daily, weekly and monthly

#

But only this one fails consistently

#

It's also the only one in the Finnish timezone

#

and then listen to payout.updated instead

azure forge
#

No the reconciliation_status moves right after the Payout is created

nova wing
#

Alright

#

I think it's weird that a payout can have a status of paid but you can't query for its contents

#

report-wise

#

If it's paid, you should know

azure forge
#

I'm still looking, but basically what is happening here is that the Payout is being created/paid on the same day. Whereas the normal flow is that we create and "queue" the Payout ~1 day ahead of time so that the funds actually land (the Payout moves to paid) on the day of the balance transaction availability.

#

That means the data is available for the reconciliation report after that ~1 day

nova wing
#

Okay. Could it help to move the payout weekday?

azure forge
#

But here it isn't ready becuase this is happening same-day

#

I'm not sure yet why this account's payouts are created/landing same-day

nova wing
#

It's a bit of a problem as I manually have to go in and re-queue for this account every week and they're annoyed that it doesn't work

azure forge
#

Yeah that's totally fair

#

Unfortunately I'm not super familiar with the intracacies of payouts since it isn't really an API focus

#

But I'm looking some more to see what I can find

nova wing
#

Thank you. I think a good solution would be to have report_data_available: <bool> on the payout object and then fire a payout.updated when it changes

#

or perhaps a new event if you don't want to add another update for BC reasons

azure forge
#

I mean sure, that would certainly fix this issue. But something like that would never be added quickly so it isn't a short-term fix.

nova wing
#

I wouldn't expect you to fix it here and now, but I still think it's something worth considering

azure forge
#

Yeah I'm happy to file that feedback

nova wing
#

I've never been asked by Stripe to "retry later" without having a webhook be able to notify me

#

so it goes against that convention

azure forge
#

Yep

nova wing
#

Let me know if you come up with something we could try

azure forge
#

Okay I think the issue is that we can't queue payouts over the weekend.

#

This account is specifically set for a Monday payout

#

Weekly

#

So the payout is created and pushed through on Monday

#

I think

nova wing
#

I believe we have others also on monday, but I can ask them to try Friday

azure forge
#

If there is another example then I'd be happy to look. Overall though at this point I'm not quite sure what else would cause this account to be unique like this. Your best bet might be asking this same question to our Support team as they actually do focus on Payout timing.

#

They should be able to identify why this Payout timing is different than your other accounts.

nova wing
#

I'm going to try and move it to Friday first and see if it solves it

azure forge
#

Sounds like a good place to start

nova wing
#

Thank you. If you could file the webhook feedback then I think that's it

#

For now