# Latency in sending webhook requests

**URL:** <https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063>\
**Category:** Webhooks\
**Created:** [June 18, 2020, 12:06am UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063 "2020-06-18T00:06:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ihwangj](https://avatars.discourse-cdn.com/v4/letter/i/6de8d8/32.png) [@ihwangj](https://community.shotgridsoftware.com/u/ihwangj)\
**Post date:** [June 18, 2020, 12:06am UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063/1 "2020-06-18T00:06:57Z")

</div>

Hi,

I’ve set up a webhook for my company instance to update the downstream task status. I’m using your code example(from siggraph 2019 tutorial) as the code base and AWS API Gateway and Lambda services to set up this webhook. However, sometimes there’s a long delay(more than 5 seconds) in updating the status. Even without the delay, the webhook takes about 3 seconds to reflect the update in the UI.  
I checked the logs on the AWS services and the actions usually finishes in 300ms from start to finished. I’m wondering if there’s a way to monitor the process on the shotgun site(I’m using a cloud instance) so I know which part may be the cause or can you provide any insight as to why there’s a delay?

Thank you

---

<div class="post-metadata">

**Author:** ![daigles](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/daigles/32/1072_2.png) [@daigles](https://community.shotgridsoftware.com/u/daigles)\
**Post date:** [June 18, 2020, 2:01pm UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063/2 "2020-06-18T14:01:07Z")

</div>

Hi,

Thank you for participating in the Webhook beta program!

We are looking into sporadic delay issues (there will be a post about this later today) but aside from these, it is normal for the webhook to take a few seconds to trigger. It would not be normal to have to wait for 1 or more minutes for the trigger to happen.

Regards,  
-Stéphane

---

<div class="post-metadata">

**Author:** ![ihwangj](https://avatars.discourse-cdn.com/v4/letter/i/6de8d8/32.png) [@ihwangj](https://community.shotgridsoftware.com/u/ihwangj)\
**Post date:** [June 18, 2020, 5:39pm UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063/3 "2020-06-18T17:39:36Z")

</div>

Thank you for the reply. Looking forward to the post.

---

<div class="post-metadata">

**Author:** ![johnny.duguid](https://sea1.discourse-cdn.com/shotgunsoftware/user_avatar/community.shotgridsoftware.com/johnny.duguid/32/4_2.png) [@johnny.duguid](https://community.shotgridsoftware.com/u/johnny.duguid)\
**Post date:** [June 18, 2020, 6:11pm UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063/4 "2020-06-18T18:11:06Z")

</div>

Link to @daigles’s post here for reference. 🙂

> [@Delivery Delays and Lost Deliveries](https://community.shotgridsoftware.com/t/delivery-delays-and-lost-deliveries/9073):
>
> IMPORTANT: Upcoming change that could cause some webhooks to fail because of timeouts. Hi everyone, Some users have recently complained about unexplained delays in the trigger of their webhook events or even losing some events. While digging into these issues we found that the max amount of time allowed for each trigger (currently 6 seconds) was not being enforced. This allowed webhook triggers to take much longer than expected to complete. Under load, this can lead to the slowdown of webhook…

---

<div class="post-metadata">

**Author:** ![Romey](https://avatars.discourse-cdn.com/v4/letter/r/e8c25b/32.png) [@Romey](https://community.shotgridsoftware.com/u/Romey)\
**Post date:** [July 8, 2020, 7:23pm UTC](https://community.shotgridsoftware.com/t/latency-in-sending-webhook-requests/9063/5 "2020-07-08T19:23:47Z")

</div>

I have also expressed my concerns about performance. Furthermore, I am pretty sure the issue is with the webhook service itself. We have a single lambda endpoint that brokers request from webhooks as well as actions. The actions appear to be much more performant since no service sits in the middle. I am just getting into AWS SQS and I am hoping that I can transition my single update webhook to batch updates via SQS and speed up the overall perceived performance of webhooks. I let you know how that goes.
