daisdead | Stripe Developers | Page 1

novel horizonBOT Jul 31, 2023, 1:17 PM

#

lethal sigil Jul 31, 2023, 1:18 PM

#

Gotcha, looking in to whether you can properly simulate that with retrieveUpcoming

rich linden Jul 31, 2023, 1:19 PM

#

I appreciate it!

wind ocean Jul 31, 2023, 1:21 PM

#

yep unfortuantely this is a known issue where the upcoming endpoint ignores that parameter

#

we're aware of it but a fix hasn't been widely released since the team doesn't have bandwidth for it(since changing it now is a breaking API change so we have to think about how to handle this for users relying on the brokenness/ignoring behaviour and etc), unfortunately.

I'd suggest writing to https://support.stripe.com/?contact=true to help raise the feedback, and I think also we can give your account special access to opt into the fix

rich linden Jul 31, 2023, 1:23 PM

#

Ah - I see! This is all good to confirm 😄

I'll work w/ team regarding this and ultimately don't think it's a blocking detail for us!

#

Appreciate it all folks! 🙏

wind ocean Jul 31, 2023, 1:25 PM

#

just curious, can you share an example sub_xxx or in_xxx account just so I can check something about if you're opted-into the fix here?

rich linden Jul 31, 2023, 1:26 PM

#

Let me know if this works sub_1NZvU3KK7do9jqjrP2KkzYzl

wind ocean Jul 31, 2023, 1:30 PM

#

the notes we have on this are a bit confusing and could read as it being the case that we fixed this 'going forward' on new accounts, but existing accounts who we detected using pending_invoice_item_interval are kept on the legacy behaviour. But I don't see your account in the list of getting the legacy behaviour

rich linden Jul 31, 2023, 1:32 PM

#

Assuming new accounts means relatively recent; I would only guess my company's Stripe account is old enough to be in the legacy bucket. Either way, the actual behavior is showing legacy details so I'll move forward knowing this

wind ocean Jul 31, 2023, 1:33 PM

#

ack; but I do think we can fix this for you if you write into support

#daisdead