# Sepasoft Web Service SOAP Consumer Timeout Setting

**URL:** <https://forum.inductiveautomation.com/t/sepasoft-web-service-soap-consumer-timeout-setting/44830>\
**Category:** Ignition\
**Created:** [March 24, 2021, 2:41am UTC](https://forum.inductiveautomation.com/t/sepasoft-web-service-soap-consumer-timeout-setting/44830 "2021-03-24T02:41:28Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![dustin.cooper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dustin.cooper/32/29963_2.png) [@dustin.cooper](https://forum.inductiveautomation.com/u/dustin.cooper)\
**Post date:** [March 24, 2021, 2:41am UTC](https://forum.inductiveautomation.com/t/sepasoft-web-service-soap-consumer-timeout-setting/44830/1 "2021-03-24T02:41:28Z")

</div>

Recently, some changes have been made to one of our ERP service endpoints that makes for longer back-end processing time, and I have need of a longer wait time for the response from the SOAP endpoint.

I have tried changing the Timeout setting from 60 to 90 seconds:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5c2679faa5545a64f4afa786bc4ae36c3d94d4ef.png)  
but regardless of this setting, I get a GatewayException for socket timeout after 60 seconds.

I am using Ignition 8.1.3 on Windows Server 2019 and the Web Services module 3.81.1 (b2102050803)

Is there some other global setting that I am missing that overrides the timeout setting per consumer configuration?