Intermittent “NoSuchKeyException (404)” in tS3List with AWS SDK v2 when multiple jobs run in parallel

[AkshataIDX]

We recently migrated to the latest Talend 8 runtime, which uses AWS SDK v2.
We have 38 Talend jobs running in parallel (one job per filter value).
All jobs use tS3List to read files from S3 using the same folder structure but different prefixes.

Only one or two jobs fail occasionally with the following error in tS3List_2:

software.amazon.awssdk.services.s3.model.NoSuchKeyException (404)
The specified key does not exist.

The strange part is:

• The same job succeeds immediately on the next run
• The S3 folder and files exist
• The failure happens only sometimes, not consistently
• Only Talend 8 shows this behavior (Talend 7.3 never had this problem)

We identified that SDK v2 performs metadata (HEAD) calls on folder-like keys (e.g., RECV/), which may not physically exist in S3 as objects. When the folder placeholder is missing, S3 returns 404 even though the prefix itself is valid.

Questions:

1. Is this a known issue/behavior of tS3List in Talend 8 with AWS SDK v2?
2. Are there recommended best practices to avoid these occasional 404 errors?
3. Is setting “Die on error = false” on tS3List considered safe for production?
4. Is there any patch or configuration available in Talend 8 to suppress folder-key metadata calls?
5. Since we run 38 jobs at the same time, could concurrency or S3 timing cause this issue?

Any official guidance or workaround from Talend for this scenario would be greatly appreciated.

[Shicong_Hong]

@AkshataIDX Please provide the following information for us to better evaluate the issue:
- Studio version (and patch version if applicable)
- Full stack trace
- A screenshot of the basic settings of tS3List component. 

Regards

Shicong

[AkshataIDX]

@Shicong_Hong ,
Thank you for the response.

1) Studio version (and patch version if applicable)
Talend Cloud Data Fabric  Version: 8
Build id: 20250927_1321-patch

2) Full stack trace
tS3List_2 (software.amazon.awssdk.services.s3.model.NoSuchKeyException) The specified key does not exist. (Service: S3, Status Code: 404, Request ID: MY71DPVDK6WV80RZ, Extended Request ID: PZ9eM9iy+gyq6xf0i3VzNF3mLXJnqZEg20A4U+abrVV+i+w77q9QqblNTUzyNuLnOf65pJz5VjE=) (SDK Attempt Count: 1)"
1760106069865,"org.talend.sdk.component.api.exception.ComponentException: (software.amazon.awssdk.services.s3.model.NoSuchKeyException) The specified key does not exist. (Service: S3, Status Code: 404, Request ID: MY71DPVDK6WV80RZ, Extended Request ID: PZ9eM9iy+gyq6xf0i3VzNF3mLXJnqZEg20A4U+abrVV+i+w77q9QqblNTUzyNuLnOf65pJz5VjE=) (SDK Attempt Count: 1)"
1760106069865, at software.amazon.awssdk.services.s3.model.NoSuchKeyException$BuilderImpl.build(NoSuchKeyException.java:150)
3) A screenshot of the basic settings of tS3List component