cancel
Showing results for 
Search instead for 
Did you mean: 

Webhook suddenly stopped working

Hi,

 

I have been using Webhook and receiving notifications from the sandbox account for the last couple of months and everything was working fine. However today suddenly the webhook notifications have stopped firing.

 

I made the webhook inactive and tried ping and it is sucessfull. However when I submit a transaction via the Virtual Terminal or through my code no notification is triggered ( I have subscribed to Payment- AuthCapture transactions)

 

I even switched the endpoint to use http//webhookinbox , but the same thing happens there, get a message for ping, but when I submit a transaction via the Virtual terminal there is no message

 

Can anyone help me find out what is going on ?

 

Also the notification history shows the following - so there was one notification delivered today and then it stopped.

 

{
"_links": {
"self": {
"href": "/rest/v1/notifications?offset=0&limit=100&from_date=7/16/2019 12:00:00 AM&to_date=7/17/2019 12:58:22 PM"
}
},
"notifications": [
{
"_links": {
"self": {
"href": "/rest/v1/notifications/9da23d44-bb2c-473c-81eb-215b6bea112e"
}
},
"notificationId": "9da23d44-bb2c-473c-81eb-215b6bea112e",
"deliveryStatus": "Delivered",
"eventType": "net.authorize.payment.authcapture.created",
"eventDate": "2019-07-16T04:44:59.243",
"webhookId": "52b926e4-c911-4e50-b06d-ee2d2ba73bea"
},
{
"_links": {
"self": {
"href": "/rest/v1/notifications/4733a36e-4794-4be2-a844-274a9a2c6d70"
}
},
"notificationId": "4733a36e-4794-4be2-a844-274a9a2c6d70",
"deliveryStatus": "Delivered",
"eventType": "net.authorize.payment.authcapture.created",
"eventDate": "2019-07-16T10:42:40.757",
"webhookId": "52b926e4-c911-4e50-b06d-ee2d2ba73bea"
},
{
"_links": {
"self": {
"href": "/rest/v1/notifications/09f36c3d-df98-491a-8862-e049be4d006b"
}
},
"notificationId": "09f36c3d-df98-491a-8862-e049be4d006b",
"deliveryStatus": "Delivered",
"eventType": "net.authorize.payment.authcapture.created",
"eventDate": "2019-07-17T05:41:58.717",
"webhookId": "52b926e4-c911-4e50-b06d-ee2d2ba73bea"
}
]
}

AnandBhagwat
Contributor
12 REPLIES 12
@kreynen

To follow up, your webhooks will not be disabled completely, I do not think. I think the one webhook
expires and then the rest are delivered business as usual. For the triggering functionality, that would be something related to your script, wouldn’t it? I think auth.nets work is done once they’ve delivered the payload.

Well, the webhook has started working again today. Not clear why or how . I have not made any changes to code or configuration. Perhaps someone from Authorize.NET can comment on this , was there a downtime yesterday for webhooks ?

AnandBhagwat
Contributor
@AnandBhagwat

Same exact thing here. For sure there was something going on with the system that was delaying or impeding webhooks from hitting endpoints. It is extremely rare. There has hardly been a week go by for the past 9 months that I don’t run at least one test transaction, and in my development phase I will often run dozens in one day to test new functionality. I run all my test on a remote server that is configured to receive webhooks. I cannot count how many times I have deleted all the records of my customers, orders, items, etc tables due to the list being too massive to deal with. I’m at over 1,500 webhooks received, and 99.5% come back within 5 seconds of hitting the pay button.

I was working with a different and newer client when this issue first came up. So after a while I switched to my heavily vetted preexisting test site url. I ran two transactions and it took over an hour for them to come back. That was at about 8 pm yesterday. After those 2 came back, things started being business as usual immediately, with instant responses.

The day before they were “down” intermittently. On and off again you would get an instant response. Like I say, first issue like this ever in going on 9 or 10 months of continuous testing.