Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 3

Extended 'Service Timeout' for webhooks

Solved! Go to Solution.

I've created a Github App that will work on our company's pull requests.

 

The Azure Functions serverless platform removes the allocated compute once the app gets cold (zero requests for >15 mins). So there is a cold start delay to get it back. This is only ~10 seconds but that plus Github login time, etc, means the first webhook of the day gets a failed delivery "Service timeout". (It is still processed fine.)

 

1. What is the allowed service timeout?

2. Can we please have a setting to increase it?

2 Replies
Solution
Community Manager
Message 2 of 3

Re: Extended 'Service Timeout' for webhooks

Hey @ishepherd,

 

Thanks for being here!

 

GitHub expects that integrations respond within 10 seconds of receiving the webhook payload, as seen in the docs.

 

At this time there is no setting to increase it, I've logged your feature request in our internal feature request list. Though I can't guarantee anything or share a timeline for this, I can tell you that it's been shared with the appropriate teams for consideration.

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 3 of 3

Re: Extended 'Service Timeout' for webhooks

Thanks @andreagriffiths11 !
Yes, please consider it. FAAS platforms are perfect for cheap/free GitHub webhook implementations - apart from this one small issue.