#angieg0nzalez_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1319080024758026320
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Request ID for a production example - req_fQCVrItAwcROKX
Hi ๐
Orders (both v1 and v2) have been deprecated for quite some time. Is this something that just started happening?
yes, but i dont know exactly when
Okay I found examples in your account logs
we understand its deprecated, just haven't had the bandwidth to migrate yet
Let me see if I can get an idea for what changed
thank you!
Hmmmm... It looks like it happened sometime on Monday. I can see that we are successfully computing tax on one request but then, a little over an hour later, we do not.
interesting. i dont think we had anything change on our end.
I'm checking on this with some of my colleagues
and it looks like this may be due to a bug on our end. I have raised this issue internally and we are getting more teammates to look into this.
thank you so much
Okay it looks like this was expected and that we reached out to your account in October. I'm still getting more details
ooh ok thank you
If i could get a copy of whatever was sent in October, that would be great.
Hmmm.... okay it looks like this is actually still internal. We did reach out but the issue is you aren't the one that needs to update the integration.
ok
We are working to undo the change right now
great, thank you!
Okay, we have completed our update. You should see successful orders coming through. If you continue to see this error, please flag it to us again.