Question & Answer

Question

Issue Description:

Users may encounter "Unable to store data" issues while running ServiceNow connectors. The issue is commonly associated with timeout conditions while fetching data from the ServiceNow endpoint.

Typical error messages include:

low space / Error copying stream; Caused by: stream is closed / Connection Reset

Cause

The most common reason for this issue is a timeout occurring while reading data from the ServiceNow endpoint. Large datasets, slow API responses, network interruptions, or ServiceNow instance limitations can contribute to these failures.

Answer

Increase API Request Timeout

Increase the API request timeout settings in the ServiceNow configuration.

Recommended Timeout Value

Set the timeout to:120 seconds

If this didn't resolve the issue, you can try below additional troubleshooting/mitigation steps.

Additional Troubleshooting Steps:

1. Verify Session Timeout Settings

Ensure the session timeout settings are configured appropriately.

Navigation: System Properties > Security

Property: glide.ui.session_timeout

Recommendation: Increase the session timeout value if sessions are expiring too quickly.

2. Review API Rate Limits

Custom API rate limits may interrupt connector executions.

Navigation: System Web Services > REST API > Rate Limits

Recommendation: Review and adjust any configured API rate limits impacting the connector.

3. Configure Web Service Timeout

Adjust outbound HTTP timeout settings.

Navigation: System Properties > Web Services

Property: glide.http.outbound.max_timeout

Recommendation: Defines the maximum timeout for outbound HTTP requests in milliseconds.

4. Review ServiceNow Logs

Check ServiceNow logs for additional warnings or failures related to API requests.

Navigation: System Logs > System Log > All

Recommendation: Search for:

timeout errors,
connection reset entries,
authentication issues,
outbound REST failures.

Additional Recommendations:

Reduce Dataset Size

Try running the connector with:

fewer columns,
smaller datasets,
reduced record count.

This helps determine whether the issue is related to API response time or dataset size.

Final Mitigation Step

If none of the above steps resolve the issue, add the following property in the ServiceNow instance:

Property Name: glide.http.outbound.max_timeout

Purpose

This property is commonly used to resolve timeout issues related to outbound REST API calls.

Check Concurrent Processes

Verify whether other heavy processes or integrations are running on the ServiceNow instance during connector execution.

High system load can contribute to:

delayed API responses,
connection resets,
timeout failures.

If possible, schedule the connector to run at a quieter time.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSSOGY","label":"IBM Apptio"},"ARM Category":[{"code":"a8mKe000000XZJgIAO","label":"Datalink Financials-\u003EConnections"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":""}]

Tips

"Unable to store data" issues for ServiceNow Connectors