#themechanic_webhooks
viscid tundraBOT
👋 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/1263053297737007118
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
gritty latchBOT
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.
- themechanic_api, 22 hours ago, 28 messages
mental sundial
Hi, let me help you with this.
No, you will need to work with 2 separate reports, unfortunately.
What challenge are you facing with handling 2 webhook events?
twilit heath
i'm updating a row in a db with the data of each one. But as i guess both will arrive very quickly, perhaps at the same time, i will have issue of concurrency while updating my row
mental sundial
I see. You could try configuring per-cell locking, or retry mechanism. I don't believe such update will take longer than timeout can wait.
viscid tundraBOT
arctic saffron
👋 taking over for my colleague. Let me know if there's any follow-up Qs I can answer!