Less Strict Webhook Timeout Rules
in progress
L
Lengthy Blackbird
We sometimes face issues when our servers are being deployed and receive a bunch of webhooks, leading to automatic disabling due to 20 timed out requests within 24 hours. It would be beneficial to have less strict rules applied, at least for the production webhook, to prevent disruptions during server deployments.
Agathe Brusset
marked this post as
in progress
Agathe Brusset
Merged in a post:
Increase the webhook server response limit of 3 seconds
G
Ginger orange Tyrannosaurus
Sometimes, we receive heavy traffic or have a deployment that might slow down the API temporarily and then the 3s isn't enough. Is there no way you can change this so that our webhook doesn't get paused. It is causing an issue for us.
Agathe Brusset
Hi Ginger orange Tyrannosaurus, thanks for flagging this — totally understand how the 3s webhook response limit can become an issue during traffic spikes or deployments and lead to routes getting paused. Appreciate the detailed context here; I’ve shared this with the team and we’ll review what options we have on our side, then follow up with you as soon as we have an update.
Agathe Brusset
marked this post as
under review