Skip to main content
All CollectionsCommon Errors
S3 Bucket Timeouts Error
S3 Bucket Timeouts Error

S3 Bucket Timeouts Error explained.

Praise Magidi avatar
Written by Praise Magidi
Updated yesterday

Step: S3 Source

Message

Error on read stream. Connection timed out after 120000 seconds.

Cause

This error occurs when testing a flow using the "test to step feature". This feature allows you to test files up to 1.6MB in size. If the file being pulled from the S3 source step is larger than this, you will get this error.

Resolution

  • Use a smaller file if you'd like to test using the test to step feature, or

  • Execute the flow using the "Execute flow" feature, it has no limit on the file size.

Please note that this will execute the entire flow and does not support executing up to a certain step. If you really want to isolate a portion of the flow for testing and you cannot use a smaller file, you can make a copy of the flow and delete all steps that you do not want to be part of the test.

Error Detail

Error on read stream: Connection timed out after 120000ms
Connection timed out after 120000ms
{
"Object": {
"message": "Error on read stream",
"statusCode": 500,
"errorMessage": "Connection timed out after 120000ms",
"error": {
"message": "Connection timed out after 120000ms",
"code": "TimeoutError",
"time": "2025-02-20T07:59:38.030Z",
"region": "eu-west-1",
"hostname": "[hostname was present but redacted]",
"retryable": false,
"statusCode": 200,
"retryDelay": 33.758889490531614
}
}
}
}
Did this answer your question?