Webhooks not working

[wildhart]

Hi,

Can you confirm whether the webhooks feature is working at the moment? I've noticed they've not been coming through for a while.

If I go to the webhooks subscription page (https://allcleargroup.simprosuite.com/s ... scriptions) and send a test webhook that doesn't come through either.

If I use postman to send a webhook to my server I can see it in the logs.

[Muqeet]

Will take a look and get back to you shortly.

[Muqeet]

We are experiencing high number of webhook request at the moment which could be why you must be experiencing delays in the message delivery. The messages are being still delivered in the orderly manner at the moment.

[sultan_kazi_]

Hi Muqeet,

I hope you are well.

I tried testing the webhooks subscription from the System Setup menu and it worked all fine but they are not working for the trigger event itself (such as creating a job). Could you please advice?

Thank you very much.

Kind regards,
Sultan

[ConsoleDev]

I can confirm I am also experiencing this issue.

I have enabled webhook notification and created a new job but did not receive a webhook request.

[robbertcha]

Hi,

We are looking into this issue now, thank you for your information.

[michelle]

Hi there, I've also had trouble with the job.created webhooks yesterday. We seem to have not received some jobs - was there a fault or some sort of delay with the webhooks?

Thanks
Michelle

[wildhart]

Hi,

I haven't seen any webhooks in my logs since 30th September...

Pressing "Test Subscription" on the webhook page doesn't come through in my logs either, but sending a manual POST to my webhook url appears in my logs instantly.

Is there a problem?

[wildhart]

Interestingly, pressing the "Test Subscription" button works for my local dev sever which doesn't use SSL. My test and live server which use lets-encrypt SLL certs don't receive the test webhooks from simpro (but they can from postman).

Maybe this is related to the expiry of the lets-encrypt root CA: https://letsencrypt.org/docs/dst-root-c ... mber-2021/

[Muqeet]

Hello Chris,

I have checked the logs for your build and from that I have found out that some of the callback is returning `SSL certificate problem: certificate has expired` and there are some timing out.

We have a 15 seconds timeout on message delivery request. Make sure to acknowledge the request and sent back the response quickly instead of processing the business logic based on that event.

I am sending you a private message with more details. Please have a look.