"Your webhook is failing"

in Development
Hi,
I receive multiple emails that a webhook for an order of June 5th 2019 is failing. This is an order that doesn't exist in our system.
Could you terminate this webhook/the retries?
{ "webhook": { "id": 3296017, "createdAt": "2019-06-05T10:56:43+02:00", "updatdAt": "2019-06-05T10:56:43+02:00", "isActive": true, "itemGroup": "orders", "itemAction": "*", "language": { "id": 1, "code": "nl", "locale": "nl_NL", "title": "Nederlands" }, "format": "json", "address": "https://api.easyads.eu/api/v2/Orders/Webhooks/Lightspeed" }
}
Thanks in advance!
Best,
Daan
Answers
Hi @EasyAds_Development,
Thank you for contacting us.
In most cases it is the URL that is no longer correct, this can be because there have been changes on your server side, due to a migration or updating the infrastructure.
My advice is to check this first and update it if necessary.
What is can see when I visit the Webhook URL is an error message that this URL doesn't support a GET method.
Please check this.
Hi @LucienVersendaal ,
Thanks for your quick response!
This should be correct, because we only support 'POST' to get update info on orders. Can you make sure the call is not being retried anymore? We don't experience any issues with any of the 10.000s of orders we keep in sync.
Best,
Daan
What I see is that you're using getting a webhooks on every event of the order
Can you try if you're only doing a post to use this:
Dear Lucien,
I would like to tap into this discussion as I've been developing order integration with lightspeed as well.
This issue at hand here is that the call is being retried more than 10 times. From the documentation I've learned that a webhook call would deflect after 10 times: https://developers.lightspeedhq.com/ecom/tutorials/webhooks/
What makes this webhook call persist in retrying beyond this boundry?
Good point about the itemAction specification. I will look into this if we could specify it further.
Kind regards,
Seth - EasyAds Developer
Hi @Seth,
What I heard from our PM(product manager) is that there were some changes is the Webhook suspend/ban logic a bit to optimize our load. As a result:
Also, we'll update our documentation.