Webhooks unreliable

[bmannz]

Hello

Just wondering whether others have found webhooks to be unreliable.
Last Thursday we found that webhooks were not received from around 5am-7pm and then between 7:30pm-10:30pm we received all the webhooks from earlier in the day (from 5:42am - 10pm). So up to 14hr delays.
There was maintenance being undertaken then so does that mean Simpro disabled web hooks during maintenance?

We see other instances where webhooks aren't generated at all when a job is edited. And this is when no maintenance is occurring.

Building an application that relies on Webhooks for reliable and responsive integration seems to not really be effective.
The idea with Webhooks is to save us having to query Simpro all the time. But if that means our application does not know when jobs have been updated in Simpro then that's not a workable option.

I see other old threads about unreliable webhooks but I was hoping as 4+ mths have passed that any early on webhooks issues may have been resolved.

Just wanting to know whether others have seen the same and if so did they go away from relying on Webhooks.

Regards
Brent

[rick.lan]

Hi Brent,

Thank you for your message and sorry for the service interruption, the interruption from last week is more likely an issue to the server then the service itself and we are still waiting for our Infra team to priovide more information.

as for webhook not generate when a job is edited, could you please provide a few examples so we can look into?

cheers,

[bmannz]

Hi Rick
I will DM you the job number for a tenant that you can look at.
But an example is a job that was updated on the 18th but below is a list of the webhooks received.
'Job #30955 has been created.', '2020-11-17 09:53:02'
'Job #30955 has been updated.', '2020-11-17 09:54:02'
'Job #30955 has been updated.', '2020-11-17 09:54:02'
'Job #30955 has been updated.', '2020-11-17 10:01:02'
'Job #30955 has been updated.', '2020-11-17 10:01:02'
'Job #30955 has been updated.', '2020-11-17 10:14:04'
'Job #30955 has been updated.', '2020-11-26 13:01:02'
'Job #30955 has been updated.', '2020-11-26 13:01:02'

During the period on the 18th we received webhooks for other jobs, but not the one in question therefore it would appear as though it was never generated.

Regards
Brent

[michelle]

Hi Brent,

I'm seeing the same intermittently and it's hard to see a pattern as it seems to be random updates that don't come through when you compare them to the simPRO logs. Muqeet is looking into one of the instances for me. Hopefully, this can be resolved otherwise it could mean having to build in a CRON workaround which could be painful (ie. costly) to implement.

Fingers crossed...

Michelle

[Michael]

Hi Guys,

Just wanted to add, we are also occasionally seeing missing webhook events as well as occasionally many hour delays in receiving webhook callbacks.

I hope/trust these issues will be resolved.

Regards
Michael

[michelle]

Hi fellow webhook users,

So I did a little research today on the webhooks and it looks like a change on the job status triggers a webhook notification however there seems to be an issue with the invoice automation. When an invoice is created on a job it automatically updates the stage and the status of the job (some companies do and some don't have this setup) but because it's handled in the back end it doesn't trigger a webhook as that seems to be only triggered from UI updates. The reason it seems intermittent is that sometimes the job is updated further which generates a webhook where the status change can then be picked up and sometimes those jobs are never modified again so you end up with an incomplete job.

Hopefully, simPRO can add that Invoice creation and subsequent status and stage updates to the webhook logic so that we can get notified. If anyone else needs this update please make yourselves known so that this issue gets bumped up in terms of priority.

Regards
Michelle