<turbo-stream action="update" target="wiki_card"><template>

<h1>E2157 – ECE_SSLError: SSL Timeout on Read</h1>
<div class="trix-content"><p><strong>Full message:</strong> <code>ECE_SSLError: We got an error from the SSL module: Timeout on SSL readData - the server took too long to respond.</code><br><br></p><h3>What it means</h3><p>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.<br><br></p><h3>Common causes</h3><p><strong>1. No source control field (timestamp field) configured :</strong> 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.</p><p><strong>2. Large dataset queried without filters :</strong> 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.</p><p><strong>3. Non-indexed filter fields :</strong> 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&nbsp; and the query times out on large volumes.</p><p><strong>4. Source system under load :</strong> 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.</p><h3>How to fix it</h3><ul><li>Add a <strong>source control field (timestamp field)</strong> to the transfer to limit each run to new or changed records only;</li><li>Apply <strong>filters</strong> to reduce the dataset being queried (e.g. by status, date range, or record type);</li><li>Verify that any fields used in filters are <strong>indexed</strong> on the source system. If not, request the index to be added or switch to an indexed field;</li><li><strong>Upgrade the service and/or connector version</strong> - each Rapidi release may include bug fixes, new functionalities, or improved timeout handling. If the error persists after addressing query scope, <strong>contact Rapidi Support</strong> to request an upgrade to the latest available version.</li></ul><h3><br></h3></div>
</template></turbo-stream>

