# SaaS Web Service Connector - Error: Command Timed Out

**URL:** <https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, identity-security-cloud\
**Created:** [August 18, 2023, 11:42am UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255 "2023-08-18T11:42:27Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [August 18, 2023, 11:42am UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/1 "2023-08-18T11:42:27Z")

</div>

Hi all,

Currently, we’re building a connection to a web service using the [Web Services SaaS](https://documentation.sailpoint.com/connectors/saas/web_services/help/SaaS_Connectivity/Web_Services/Integrating_SailPoint_Web_Services.html#_gl=1*c3wymg*_gcl_au*ODMzNDA5OTA2LjE2OTAyODk3Njc) connector connector (not to be confused with [SaaS Connectivity](https://developer.sailpoint.com/idn/docs/saas-connectivity/)). It seems however, that there is a limitation in the processing of the data, since we get a _“Command timed out”_ error message when we start to map a lot of the data.

According to [this post](https://developer.sailpoint.com/discuss/t/timeout-errors-from-cloud-connector-after-it-completes/8198/7) it seems it must be a setting in IdentityNow (that we cannot change ourselves)?

Is there another way out, besides implementing pagination?

Thanks in advance!  
Edwin

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [August 18, 2023, 12:22pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/2 "2023-08-18T12:22:08Z")

</div>

SaaS connectivity doesn’t have unlimited memory, so you have to use pagination to process large amounts of identities. If running out of memory isn’t your issue, and your command is just taking longer than 3 minutes to process the request, then you can issue an `res.keepAlive()` in your code to keep the command from timing out. Please see this doc for more information.

> **[Connector Timeouts | SailPoint Developer Community](https://developer.sailpoint.com/idn/docs/saas-connectivity/in-depth/connector-timeouts)**
>
> IdentityNow will throw an error if your connector does not send a response in 3 minutes. For connector commands that might take longer than 3 minutes, make sure to send data at regular intervals to prevent a timeout.

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [August 18, 2023, 12:37pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/3 "2023-08-18T12:37:55Z")

</div>

Hi Colin,

Thanks for the quick reply.

This is NOT a custom connector, so I don’t have any code here. This is using the Web services SaaS connector from SailPoint. Any idea if there is a way to force the keepAlive in that connector?

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [August 18, 2023, 12:53pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/4 "2023-08-18T12:53:13Z")

</div>

Oh, sorry about that. When you said “SaaS based web service connector” I thought you were referring to SaaS connectivity. You’re talking about the VA based web service connector.

You should be able to increase the timeout of VA connectors. Follow the solution here:

> [@Increase timeout](https://developer.sailpoint.com/discuss/t/increase-timeout/12545):
>
> Hi, Is there an option available to increase the timeout value for a source in identitynow.

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [August 18, 2023, 1:02pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/5 "2023-08-18T13:02:40Z")

</div>

In this case it’s option number 3, it is the new Web Services connector that runs directly in IdentityNow, so without the VA.

[https://documentation.sailpoint.com/connectors/webservices/help](https://documentation.sailpoint.com/connectors/webservices/help) → good old VA based web services connector

[Integrating SailPoint and Web Services SaaS](https://documentation.sailpoint.com/connectors/saas/web_services/help/SaaS_Connectivity/Web_Services/Integrating_SailPoint_Web_Services.html) → SaaS based web services connector

I’m assuming the second is based on the SaaS connectivity technology, but I’m not sure.

So is there a way for this ‘out-of-the-box’ connector to be configured with a keepAlive?

---

<div class="post-metadata">

**Author:** ![philip-ellis](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/philip-ellis/32/502_2.png) [@philip-ellis](https://developer.sailpoint.com/discuss/u/philip-ellis)\
**Post date:** [August 18, 2023, 1:23pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/6 "2023-08-18T13:23:30Z")

</div>

I think the only way the new SaaS based webservices connector will keep the connection alive is if you send a response within 3 minutes, usually done through pagination logic. Otherwise it will timeout. For any complex webservice calls that need to be made, we recommend to simply create a [custom connector](https://developer.sailpoint.com/idn/docs/saas-connectivity/) using the SDK.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [October 17, 2023, 1:23pm UTC](https://developer.sailpoint.com/discuss/t/saas-web-service-connector-error-command-timed-out/16255/7 "2023-10-17T13:23:47Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
