First, thanks for the 2026 release, the .NET 1 are very welcome here.
We use this component to deliver files to an SFTP endpoint. Each delivery is a single zip containing a claim's XML plus the customer's uploaded attachments (scans and photos of invoices). When attachments push the zip past ~5.5MB, the call fails before it reaches the library:
OS-BERT-ELR-61301 - Error executing action Input payload is too large (10.27MB), maximum allowed is 5.50MB.
This is the documented ODC limit on external library input parameters, so it isn't something the component is doing wrong, but it does make `Put` unusable for any file over that size.
Would you consider adding an action that lets the library obtain the bytes itself rather than receiving them as a parameter?
Hi Erik,
A workaround that should work while the owner looks at this: upload the zip to S3 (or similar), generate a pre-signed URL, and have a small custom external library receive only the URL + SFTP details, download the file and upload it with SSH.NET. That way the bytes never go through the ODC parameter.
The official UltimatePDF ODC library uses the same approach with its ToS3 action: https://github.com/OutSystems/UltimatePDF-ExternalLogic
Just keep in mind the 95s timeout for external logic mentioned in that README.