#geekcorner_best-practices

1 messages · Page 1 of 1 (latest)

safe sluiceBOT
hollow capeBOT
#

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.

safe sluiceBOT
#

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

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

light dawn
#

And I figured out I couldn't add more characters to my message, but got enough place to ask all of my questions 😄

stuck kestrel
#

Hi,

  • "Webhook endpoints might occasionally receive the same event more than once" Are we talking about several times in a few minutes? Or several days? I'd like to know whenever I can simply put the IDs in Redis or if I need to store them in the database instead

There is not a specific cadence that we can share with you I'm afraid. The recommendation is to log the event IDs you’ve processed so you keep see if you've already processed that event.

  • "Handle events asynchronously" I got a working BeeQueue with Redis setup. Would that work?

I am not too with B eeQueue with Redis setup, if you can share your specific concerns, I'm happy to further look.

  • Related to the previous one and "Quickly return a 2xx response" Does that means I can simply verify the webhook signature then send the returned payload to my queue?

Generally speaking, yes, but I feel like there is more to the question.. Is there?

light dawn
stuck kestrel
#

We recommend that quickly return a successful status code (2xx) prior to any logic. I do not know enough about beequeue so I can't speak to that. You'd want to verify the signature and then return a successful status code (2xx), then run any logic on your end.

light dawn
#

shouldn't I send the payload into my queue before?

stuck kestrel
#

You mentioned 'BeeQueue with Redis setup' earlier which I do not know anything about so I can't speak to that. The 200 tells Stripe that you recieved the webhook event on your end.

light dawn
#

basically a queue-worker lib for nodejs

#

and it uses redis

stuck kestrel
#

In that case yes.