#oms-baunz_error
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/1367131257997230120
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there ๐ making sure I'm understanding correctly, you're saying you made a request to our API that returned an error but then also took the intended action?
Can you share the ID of that request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
I'm assuming you mean this - req_dtAvRMweCWON1L
(sorry first time here ๐ )
and yes, that is correct, API returned error, but intended action worked - PI shows as CANCELED when retrieving it with reason - "abounded"
ok, you can ignore me I'm an idiot - I returned error code from the WEBHOOK, so the "error" is a RETRY of the SEND being handled again - I'll sort out the code to always return 200 when handled
if we are on this subject already though and you see this - is it possible to return something like:
Response.json({ received: true }, { status: 401 });
so the WEBHOOK is not re-triggered but I still see the logs in dashboard ?
Sorry, the server is pretty busy at the moment and it's taking me a bit to get to everyone.
You can't send a status outside of the 2XX range if you don't want us to try to deliver the Event to your endpoint again, but you should still be able to include a resopnse even on success and that will appear in your Stripe dashboard I believe.
I do think the error you received in the request is misleading, because the intent seemed to not be able to be canceled because it had already been canceled, which is not what that error message conveyed to you. I'll take that back to our teams as something for us to work on.
thanks @violet anchor - highly appriciate it - I'll stick to 200 code for now ๐
Any time!