We are considering changing the maximum REST/SOAP timeout. any consequences with this change?

[Ravish Shetty]

Hi all,

We are considering updating the following properties:

• glide.http.outbound.max_timeout.enabled → true
• glide.http.outbound.max_timeout → 180

The current timeout setting is 60 seconds.

This change is being evaluated because one of our outbound integrations is failing due to timeout. The integration is vendor-supported, but so far, the vendor has not provided any recommendations. We are exploring options to stabilize the integration, and initial tests show improved results when the timeout is increased.

Could you share any insights on the potential impact of making this change?

Thanks,
Ravish

[Dr Atul G- LNG]

Hi @Ravish Shetty 

Generally, we go with the out-of-the-box (OOTB) limit only, but if you have a strong business case and need to extend it to 180, there is no impact.

https://www.servicenow.com/community/developer-articles/outbound-integrations-using-soap-rest-perfor...

[Ankur Bawiskar]

@Ravish Shetty 

yes there will be performance impact

Best practices for handling scriptable outbound REST and SOAP messages on the Now Platform 

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[Dr Atul G- LNG]

Check this as well:

https://noderegister.service-now.com/kb?id=kb_article_view&sysparm_article=KB0716391