#emgee_api

1 messages ¡ Page 1 of 1 (latest)

boreal tulipBOT
brittle terraceBOT
#

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.

boreal tulipBOT
#

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

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

placid holly
#

Hello

#

Taking a look

cursive kindle
#

Something to add. Noticed that the status code returned for req_T8h43IXBfve9jl was 404 rather than 400. Not a big deal, but seemed off given the error:

 "message": "You cannot update a subscription that is `incomplete_expired`.",
placid holly
#

Yeah I think this was just an oversight

#

I'm getting a sanity check from a colleague but I don't see any real reason why we would prevent a metadata update here

#

So mostly I think I'm going to need to just file a ticket internally requesting that this validation is relaxed

#

Also, yes, the HTTP status should be the same here.

#

I'll request that gets fixed as well (for the errors when applicable)