Issues
When you try to establish or maintain a network connection between Unstructured and an external system, you get one of the following error types:ReadTimeoutTimeoutErrorServerDisconnectedErrorClientConnectorError: For example, acannot connect to localhosterror.ConnectionError: For example, aFailed to resolve 'model-registry-api...error.ServiceResponseError: For example, for Azure, aTimeout on reading data from socketerror.ClientPayloadError: For example, aResponse payload not completedorConnection reset by peererror.OSError: For example, for Amazon S3 during a file upload, an[Errno 22] The request body terminated unexpectedlyerror.
Possible causes
- Unstructured failed to connect to a required system.
- The connection timed out while waiting for a response.
- An established connection was unexpectedly closed.
- Transient network issues were encountered with the local network, with the Internet, or with a cloud provider.
- Firewalls are blocking connections.
- Some services are temporarily unavailable, slow, or unresponsive.
- The processing of very large files is causing long-running operations, which lead to exceeding default timeouts.
- Issues with DNS resolutions were encountered.
Possible solutions
- Retry the job: Many network errors are transient. Wait a few minutes and then retry the job.
- Check network connectivity: Ensure stable network connectivity with the related source and destination systems.
- Check firewalls: Verify that any firewalls are not blocking necessary connections to source or destination APIs, blob storage, databases, vector stores, or ports.
- Process smaller batches or files: If timeouts occur during processing or uploading very large files, try using smaller files or batches.
- Contact Unstructured Support: For persistent
ClientConnectorError,ConnectionError, or other frequent timeouts or disconnects that aren’t resolved by retries, contact Unstructured Support. These issues can sometimes point to internal Unstructured system problems.

