You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have implemented the handling of webhooks for a selection of events and that works perfectly fine.
We recently received duplicate webhook messages from Moneybird, specifically for the same sales_invoice_send_email event. Here are the sanitized entries from our web server logs:
You can clearly see that the first request received a 200 response.
My questions are whether anyone has experienced this before and what the best approach would be to prevent this from creating duplicate invoices other than using the framework (Laravel in this case) or database by making the invoice number column unique?
If this can happen with this type of event, it could also happen with other Moneybird events where column uniqueness doesn't help.
The text was updated successfully, but these errors were encountered:
We have implemented the handling of webhooks for a selection of events and that works perfectly fine.
We recently received duplicate webhook messages from Moneybird, specifically for the same
sales_invoice_send_email
event. Here are the sanitized entries from our web server logs:You can clearly see that the first request received a 200 response.
My questions are whether anyone has experienced this before and what the best approach would be to prevent this from creating duplicate invoices other than using the framework (Laravel in this case) or database by making the invoice number column unique?
If this can happen with this type of event, it could also happen with other Moneybird events where column uniqueness doesn't help.
The text was updated successfully, but these errors were encountered: