---
title: "E2157 – ECE_SSLError: SSL Timeout on Read"
description: "E2157 – ECE_SSLError: SSL Timeout on Read"
keywords: "E2157 – ECE_SSLError: SSL Timeout on Read"
url: "https://myrapidi.com/wiki/e2157_ece_sslerror_ssl_timeout_on_read"
locale: "en"
published: "2026-04-17T16:13:48Z"
modified: "2026-04-17T16:13:48Z"
---

**Full message:** `ECE_SSLError: We got an error from the SSL module: Timeout on SSL readData - the server took too long to respond.`

### What it means

The source system accepted the connection but did not return data within the allowed SSL read timeout window. The integration timed out while waiting for a response.

### Common causes

**1. No source control field (timestamp field) configured :** The transfer has no timestamp field meant to read only what has been created and/or updated since the last run. instead it queries the full dataset every time it runs. A full dataset query on large tables will eventually exceed the timeout threshold.

**2. Large dataset queried without filters :** No filter conditions are applied to the source query, causing the system to attempt a full table scan. On large datasets, this takes too long and the connection times out before data is returned.

**3. Non-indexed filter fields :** Filters are in place, but the fields used are not indexed on the source system. Without an index, the database performs a full scan anyway, making filters ineffective for performance  and the query times out on large volumes.

**4. Source system under load :** The source server is busy (e.g. during business hours, batch jobs, or backups running in parallel). Even a well-scoped query can time out if the server has insufficient resources at that moment. Intermittent occurrences of this error are a clue.

### How to fix it

- Add a **source control field (timestamp field)** to the transfer to limit each run to new or changed records only;
- Apply **filters** to reduce the dataset being queried (e.g. by status, date range, or record type);
- Verify that any fields used in filters are **indexed** on the source system. If not, request the index to be added or switch to an indexed field;
- **Upgrade the service and/or connector version** - each Rapidi release may include bug fixes, new functionalities, or improved timeout handling. If the error persists after addressing query scope, **contact Rapidi Support** to request an upgrade to the latest available version.

###