sameermoin wrote:Hi Everyone,
I enabled webhooks and subscribed for an event Inventory.Updated
Not a hell of a lot to go with here.
You need to make sure the WebHooksHostURL is reachable from the clients. This URL needs to be the URL of the Jiwa API.
A common mistake is to put
http://localhost - which will work only from instances of Jiwa on the same machine as the API is running.
Another common mistake is using the public external DNS name without the correct hosts file entries or DNS records in place. One must be mindful of the network architecture and firewalls.
A simple test is to try putting the contents of the WebHooksHostURL into a browser on all machines expected to trigger a webhook - if it shows the Jiwa API metadata page, then that means it is reachable and should work.
Another place to look is in the SY_WebhookMessage and SY_WebhookMessageResponse tables. Using the API to look as you are won't reveal problems where the client could not reach the API to send the webhook in the first place - however, clients will fail over into an insert of these tables and will have messages in there the API won't know about until you restart the service.
From the screenshots you've provided my money is your WebHooksHostURL is not set correctly.
EDIT: I see I responded before you had added more information to your post.