I observed that when the dasher closes the order sometimes dropoff_verification_image_url is not coming with a webhook payload for DASHER_DROPPED_OFF event.
But after a couple of seconds, we can see the same property in the delivery status API endpoint https://openapi.doordash.com/drive/v2/deliveries/%7Bexternal_delivery_id%7D
Any help would be appreciated.
Thank you
Related
I’ve set up a very basic Zap with a vFair trigger. The trigger uses a Webhook. The trigger is fired when somebody registers for a specific event in vFair, (there is only one event set up).
The problem is that only a few of the registrations in vFair are triggering the Zap, others do not appear in the Zap history at all. This makes it very difficult to troubleshoot - from vFair’s side they can show that the webhook has triggered in their logs, but in Zapier there is no record of the record being received.
Can anyone shed any light on how to find the cause and fix it?
We are expecting every event registration in vFair to trigger the webhook and send a record to Zapier, but this only happens intermittently. We could have four even registrations in a space of five minutes, of which two trigger the Webhook and two do not.
Once in a while, my API calls to Acumatica will not return a response body, but still return a 200. The same call will be successful after a few minutes.
My guess is that I might be hitting limitations on the number of API requests per minute, or concurrent requests. It's hard to know when the requests are coming back as 200. There are no response headers that indicate an error.
Has anyone else experienced this?
I think you're on the right track regarding reaching a limit. I have experienced delayed requested but not declined requests from the API. There is definitely a limit based on the license on the Acumatica site. You should be able to take a look at the License Monitoring Console screen in Acumatica to see if there are any API violations -- Number of transactions per minute, delayed transactions and declined transactions are all logged and shown in the statistics on this page.
The image below shows an example of this page.
We have active subscriptions created with a GraphWebHook and everything has been running fine for last 4 months. Suddenly today we do not receive any notification from Microsoft o365 server. What could be the problem and how can we trace the issue. Fiddler shows nothing is sent to out WebHook when we change in outlook.
Any help greatly appreciated.
Thanks
Anamika
Having the same problem. One event was signaled but nothing else. Get /subscriptions shows active subscriptions but none are being received.
I've created a telegram bot and set a webhook as described in the docs. For testing purposes I've set it up so once you send the bot a message it replies back with the same message.
Now the issue I am having is that the updates from telegram are coming back really slowly and there are some messages I haven't received yet. Am I missing something or is the webhook method just really slow?
I had the same problem. Turns out I wasn't responding the telegram server after I got the POST request. Due to this, the server wasn't sure if I got the previous updates and was constantly sending my webhook past updates.
I have an express server and I added this bit of line after handling the POST Request.
res.sendStatus(403)
You can also confirm this by going to this url
https://api.telegram.org/<token>/getWebhookInfo
You'll see a property called pending_update_count. It should zero or close to it.
I have setup a webhook for install event. I would like to know what will happen if my site is down. Will the webhooks get retried incase of non 200 response codes.
That's a good question! Branch does not automatically retry webhooks in the case of a non 2xx response. However, Branch does allow you to go through and see every single time they have tried to fire a webhook. In the case of a non-2xx response, you would see a red 'X' next to the record. From there you can manually re-send said webhook to your server.
If this post does not resolve your issue(s) please ask more!