teelu_api

[low dove]

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

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

[native dawn]

Hello

Taking a look

Is this error only happening on the Upcoming Invoice endpoint?

Or are you also seeing this on actual Subscription application

[zealous sleet]

looks to be on the preview, but our integration does a preview to show the totals before we can apply the changes

ill check on the purchase shortly

[native dawn]

Thanks, we are investigating on our end as well. Does indeed look like something is amiss

[zealous sleet]

our update endpoint on our integration does a preview on the changes to determine whether we want to prorate the charges (our business logic prior to applying the update to the subscription) so that is also not working correctly at the moment

[native dawn]

Gotcha, we have flagged internally and we are investigating

[zealous sleet]

looks like the request to update the subcription does go through with the promo code, req_rCG0bbizePv8CN

[native dawn]

Thanks, I believe we have found the issue.

I'll circle back as soon as we have confirmed

[zealous sleet]

Hey @peak bolt! its been a while since i've had you jump in on a thread for a bug, hope you're doing well!

[peak bolt]

Hi 👋

My colleague and I are monitoring this situation. We will get back to you once we have a resolution. We appreciate your patience with this issue.

[zealous sleet]

Is there a rough eta? if not, ill check back every so often throughout the day but might not respond immediately if im busy at the time

[native dawn]

ETA is about 45 mins I'd say

Could be a little bit longer

But we are working on a fix as we speak

[zealous sleet]

Awesome, appreciate it @native dawn 👍

[native dawn]

Thanks for reporting

[zealous sleet]

Thank you as well for jumping on this so quickly

[lofty seal]

Hello
Taking over here.. We expect the issue to resolve shortly. So I'm going to close out the thread.

If you're still seeing the issue, feel free to open a new thread or write in via our support page
https://support.stripe.com/?contact=true

[zealous sleet]

Ummm can we not close this until its been completed?

I have been waiting and don't want to start a new thread just to verify the fix

[native dawn]

Yeah I'll keep this open. Fix is almost deployed, few more minutes

[zealous sleet]

Thank you, i'll run tests on my end to verify as well

Looks like things are working again 🙏

[native dawn]

Glad to hear it!

[zealous sleet]

For a bug like this, would it be included in any changelogs? or anything to link to?

[native dawn]

No not really.

[zealous sleet]

so is this thread the only real link to a bug existing?

[native dawn]

You could always reach out to our Support team and they can verify that it occurred.

Sometimes there will be proactive emails sent out about it -- that generally depends on the bug and impact.

I don't know if that will occur for this specifically.

But we don't really post something like this on a changelog.

[zealous sleet]

Okay, I was hoping for something to link with our internal bug tracking, but I'll use this thread for now.

[native dawn]

Yeah sorry I don't really have something better for you unfortunately.

[zealous sleet]

Thank you @native dawn @peak bolt @lofty seal for all the help!