#ryan_webhooks

1 messages ¡ Page 1 of 1 (latest)

flint flintBOT
#

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

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

hallow hollow
#

hi there! that email is sent when we receive error responses from your webhook endpoint. looking through your event logs I can see some examples (like evt_3RfrHTFpjXOrnwjU1QHT80OD and evt_3RfrHTFpjXOrnwjU1WfPR99d) that are failing. I would recommend checking your webhook endpoint code to see why those are failing

#

you can also refer to this guide for addressing common problems https://support.stripe.com/questions/webhooks-what-to-do-when-the-http-status-code-starts-with-a-four-(4xx)-or-five-(5xx)

Webhooks: what to do when the HTTP status code starts with a four (...

Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.

midnight bridge
#

Hey Denton, I apologize, I have very little developer backgorund. How do I check my endpoint code?

hallow hollow
#

I see, do you know who implemented your webhook code?

midnight bridge
#

I did like a month ago, but I tested it, and it successfully processed.

#

I have developer experience, its jsut really limited regarding webhooks and apis

#

so this all way over my head.

hallow hollow
#

if it helps, I've noticed that the failures seem concentrated to just two event types: payment_intent.payment_failed and charge.failed

#

so I would look at the portion of your code that may be handling those event types (or if you don't have a specific section for that, that could be the issue)

midnight bridge
#

Ok for context, we are using the gravity forms add-on for implementation. All donations are done through gravity forms on our site.

#

from the fornt end, everyhting looks like its configured correctly and working correctly. And I did notice all the events are referring to a different webhook, so is it possible this webhook I am receiving the message for is a webhook that is nto being utlized?

#

I also did not originally create these webhooks, so I'm not 100% sure why we have 3 of them in our account.

hallow hollow
#

I'm not really familiar with gravity forms, but you might check to see if they have a support channel if the webhooks were implemented through them

midnight bridge
#

Ok, yea again I was not the original person who created these webhooks, so I can't answer as to why my clients account has them.

#

question, if I did connect a different webhook to the forms, why would events possibly still be happening to this other one? I would imagine all events would just be routed through the one who's keys were implemented onto the site?

hallow hollow
#

can you give me an example of the different webhook you're referring to?

midnight bridge
hallow hollow
#

got it, so if you have multiple endpoints listening to the same event types, we'll send events of those types to all of them

#

like in your example, the endpoint without the &fid=29 querystring is configured to receive all events regardless of type, so payment_intent.payment_failed and charge.failed are also sent there

midnight bridge
#

Ok, I guess for now, I won't stress too much. It looks like donations are still working, I'm almost positive I have that other webbook implemented anyways, so as long as I am not receiving an emial regaridng that one, everything should be fine.

hallow hollow
#

sounds good, if you do notice anything else strange about your event processing, feel free to reach out

midnight bridge
#

Ok I will. Thank you Denton! appreciate your help.