I have multiple scenarios that “used to” work flawlessly with AWS. But after a few days of running, all the uploads to AWS stopped working and they give timeout error. Even for uploading a 30kb image!
Which is very strange because they were working fine. I didn’t make a change anywhere.
The error is
This module timed out
The operation timed out
Error messages or input/output bundles
This module timed out
The operation timed out
Code: ModuleTimeoutError
===========
Input
Bundle 1Collection
DataBuffer, codepage: binary
89 50 4e 47 0d 0a 1a 0a 00 00 00 0d 49 48 44 52 00 00 06 88 00 00 02 02 08 02 00 00 00 73 d9 d8 d1 00 00 00 01 73 52 47 42 00 ae ce 1c e9 00 00 00 6c 65 58 49 66 4d 4d 00 2a 00 00 00 08 00 04 01 1a 00 05 00 00 00 01 00 00 00 3e 01 1b 00 05 00 00 00 01 00 00 00 46 01 28 00 03 00 00 00 01 00 02 00 00
All data was processed, but the data was too large to log. The original size was 35.5 KB.
SHA1 checksum: 12345678***
Bucket opus-videos-12345***
Region eu-north-1
File name Logo.png
The issue is only with AWS S3 upload. Not sure why it broke if it was working for a few days.
How is it that suddenly it times out?
We are aware of the issue affecting the AWS S3 > Upload a File module, where it is returning ModuleTimeoutError errors.
This issue has been escalated to our Development Team for investigation.
Thank you for your patience. We will promptly notify you as soon as we have more information or an update to share.
@vendy can you please have the team look at this. No errors are being shared just that the upload a file module gets timed out. Its been working for years on scenarios and now happening all across our organization nothing was changed on our end.
Thank you all for raising this in the community and keeping others up to date. As @Mr.Make mentioned, there is an ongoing issue affecting the AWS S3 > Upload a File module. Our engineers are aware of it and are currently investigating the cause of the issue.
We apologize for the frustration and inconvenience. I’ll update this topic as soon as we have some information regarding the issue.
Our developers were able to identify the cause of the issue and a fix was deployed. Could you please retry your scenarios and confirm the error doesn’t appear anymore?